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
This made sense originally, but it's a bit weird now. This should probably be a map from package names to the file that was loaded, maybe paired with its load time. It should also be exported with a name like LOADED (to correspond with LOAD_PATH).
This is coming up now because I want to close the package interactions issue and the natural way to do that would be to have a map from package names to thunks to call and just let the programmer manipulate that map. Something like this:
LOAD_HOOKS["Color"] =function()
# stuff to do when the Color package is loadedend
The text was updated successfully, but these errors were encountered:
Is it coincidence that I was working on #6195 tonight (which is a version of LOAD_HOOKS which avoids needing to use eval, so it should be possible to statically compile the result)?
Package list is currently a map from absolute file paths to a floating-point load time:
This made sense originally, but it's a bit weird now. This should probably be a map from package names to the file that was loaded, maybe paired with its load time. It should also be exported with a name like
LOADED
(to correspond withLOAD_PATH
).This is coming up now because I want to close the package interactions issue and the natural way to do that would be to have a map from package names to thunks to call and just let the programmer manipulate that map. Something like this:
The text was updated successfully, but these errors were encountered: