List view
Migrating C API-based interfaces to the FFI is likely to improve performance greatly - and who doesn't like that?
No due date•0/3 issues closedWhere it seems feasible, compatibility with the wider Lua ecosystem should be enabled at the runtime level
No due date•0/3 issues closedInstalling and using external libraries that don't ship with the runtime should be a seamless experience
No due date•1/10 issues closedSupport for integrations with third-party software or built-in tooling that improves the development experience will be needed
No due date•5/11 issues closedEvents should be managed by a global event registry to provide observability and a standardized API over callbacks
No due date•4/7 issues closedSome basic tooling to develop native multimedia apps could be included (the specifics will require some iteration)
No due date•15/26 issues closedCan create HTTP and WebSockets servers (and possibly clients) that integrate seamlessly with the existing event loop
No due date•3/17 issues closedStandard Lua and C/C++ analysis tools should be employed to uncover and fix potential issues in the codebase
No due date•4/11 issues closedSimilar to a REPL but with a proper editor? Could display previews, live reload with FS watcher? (Just an idea, details TBD)
No due date•1/2 issues closedA browser context should be managed by the runtime that can be used to run and interact with web apps asynchronously
No due date•6/13 issues closedAll the existing (tested) features from the Luvi-based C runtime are available in the revamped C++ version
No due date•32/37 issues closed