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
Hey,
I will add some context info to the readme. Just to tell you up front, here are some details. This project is a great source of learning for me right now. The focus/order of implementation lies in doing all the things first which are most challenging/ require some base works to be done.
So, put differently, the focus is not about being feature complete for some class method sets. It's rather about building hard stuff first like Kernel.require as a function for its necessity of evaluating ruby code "dynamically".
The next things on the list will be
classes
Module.include
class methods
function blocks
undef
define_method
alias
....
The order is not fixed, but maybe you can see that the pattern lies more in tackling the complexity of the interpreter code with each new and more advanced feature.
At this early stage there is nothing done for performance optimizations because I have no clue what other challenges will come up when tackling meta programming topics.
Hope that helps unless I am able to add something useful to the Readme. Or maybe I will just link this issue.
Hello! :) It would be awesome to see some context about the project in the readme.
Who is this for? What is the goal? Is this for learning or eventually for some production use? What are the a caveats and tradeoffs?
Thoughts?
The text was updated successfully, but these errors were encountered: