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
To avoid the cost of requiring fennel if you want to do "low level" stuff, a/some hooks would be nice.
There is probably only one real place to hook which is just after we require Fennel. Adding other hooks for will-load-module|macro or will-compile-module|macrocould exist but are probably not that useful?
will_compile= {}
configure_fennel= {}
on|for|with|when|has_fennel= {}
when_load_fennel= {}
required_fennel= {} -- might cause confusion around regular "require fennel"-- not popping the hook, though that could be made to work easily.-- allows for future hooks in namespacehook= {
will_compile= {}
}
on= {
require(d?)_fennel= {} -- requireD because we call *after* require, not intercepting require.
}
And also a question of once or many times. Do you want to configure fennel (once) or run a hook on every compile (many), why?
The text was updated successfully, but these errors were encountered:
RE: #33
To avoid the cost of requiring fennel if you want to do "low level" stuff, a/some hooks would be nice.
There is probably only one real place to hook which is just after we require Fennel. Adding other hooks for
will-load-module|macro
orwill-compile-module|macro
could exist but are probably not that useful?and a hook would just be a function that accepts fennel and returns ... true|nil,error? Probably the hook should just raise if they have an error.
Mostly this is just a question of names:
And also a question of once or many times. Do you want to configure fennel (once) or run a hook on every compile (many), why?
The text was updated successfully, but these errors were encountered: