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
Right now, information from flags is passed around through the code-base, often having to be passed into several different functions before the information is used.
Likewise, some information like formatting information should exist and be explicitly in a single location in our code.
One way to deal with these issues is to write a new module that acts like an event-log/event-stream, possibly called log.ml, to handle such information.
The text was updated successfully, but these errors were encountered:
I don't think I understand this suggestion. Config information must travel from the front-end of the tool to the location where it is used, so what does it mean for it to exist "explicitly in a single location"?
Generally using state passing style or a state monad are the standard ways to transport this information in a functional program. Certainly we could be more uniform, in this respect.
Right now, information from flags is passed around through the code-base, often having to be passed into several different functions before the information is used.
Likewise, some information like formatting information should exist and be explicitly in a single location in our code.
One way to deal with these issues is to write a new module that acts like an event-log/event-stream, possibly called
log.ml
, to handle such information.The text was updated successfully, but these errors were encountered: