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
In the #80 conversation, it was noted that if in the future we would want to replace python with wren files for building wren_cli, it would be needed to compile a wren_cli before compiling the final version. Hence creating a need for having a wren_cli before having a wren_cli.
One possibility for solving this is using a cached versions of the wren_cli modules. That way a transitional wren_cli can be built only for executing the future wren scripts needed for compilation:
Ruby: It's not solving any particular problem that has impact while working on the cli, and is unnecessary complexity at this time. (not referring the to new line fix).
I think "at this time" can be read optimistically as "it might be nice to have one day, but it doesn't really help us out right now"... and [a bit] sadly I think I agree. I feel like someone would have to show that Python3 is a truly onerous requirement to get any traction on this (in the immediate future).
In the #80 conversation, it was noted that if in the future we would want to replace
python
withwren
files for buildingwren_cli
, it would be needed to compile awren_cli
before compiling the final version. Hence creating a need for having awren_cli
before having awren_cli
.One possibility for solving this is using a cached versions of the wren_cli modules. That way a transitional wren_cli can be built only for executing the future wren scripts needed for compilation:
cached modules can be called inside
modules.c
with a compiler flag.A possible value for
modules_cache.h
modules_cache.h
The text was updated successfully, but these errors were encountered: