You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the repository contains code for various contrib functions.
While everything is disabled by default, and can be enabled with build flags. it would be nice to have these in a separate repository as they are usually not needed when embedding rye.
Maybe the builtins can also be extracted from the evaldo into their own package.
The text was updated successfully, but these errors were encountered:
Hi, thank you for posted isues. For first few "years" (I think), contrib was a separate repository and a submodule in rye repository. But since it was a constant complication to get started with Rye and with updating it to latest state at some point I decided to just make it a normal folder in Rye, at least for now. So right now, I wouldn't change this back, unless you know for some better approach than submodule.
Making Rye-front was also an experiment on how you could extend Rye from "the other side" or externally. And it proved a good idea as we were able to reuse all Rye code, also for main binary / repl ... but it's still an open experiment.
I agree the builtins should move out of evaldo yes. So this should be done at some point.
Currently main goal is to unify the native terminal "liner" and the "wasm / browser" liner, microliner. Another developer is working on autogenerating Fyne bindings. And I have some open experiments, so moving builtins out of evaldo wouldn't be done right now but we will find time for it at some point soon.
refaktor
changed the title
Extract contrib and other extras from rye
IMPROV: Extract contrib and other extras from rye
Oct 7, 2024
Currently, the repository contains code for various contrib functions.
While everything is disabled by default, and can be enabled with build flags. it would be nice to have these in a separate repository as they are usually not needed when embedding rye.
Maybe the builtins can also be extracted from the
evaldo
into their own package.The text was updated successfully, but these errors were encountered: