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
I tried using cradle to write a helper for limiting system resources with systemd, but ran into the problem that only the Cradle module is exposed, and that doesn't expose the Input class method, or the ProcessConfig type. I think those should be re-exported from somewhere. But more importantly, maybe all modules should be exposed, even if with an Internal name? Otherwise anyone who has an unforeseen use case has to fork the library.
The text was updated successfully, but these errors were encountered:
Yeah, I think we should expose all modules. I wouldn't do that in an Internal module, since I think it's fine to just bump the major.minor versions often, at least in the beginning.
For writing your own Input or Output instances you do need to understand some of the internals of cradle so maybe we could have a warning somewhere about that.
I tried using
cradle
to write a helper for limiting system resources with systemd, but ran into the problem that only theCradle
module is exposed, and that doesn't expose theInput
class method, or theProcessConfig
type. I think those should be re-exported from somewhere. But more importantly, maybe all modules should be exposed, even if with anInternal
name? Otherwise anyone who has an unforeseen use case has to fork the library.The text was updated successfully, but these errors were encountered: