Modular Explicit branch and nofunc style

[mbarbin]

Dear Prefacers,

With the modular explicit feature on the corner I wonder if you'd have an interest for creating a long-lived experimental branch in this repo where we could explore a defunctorization of the code. I'm thinking where preface currently exposes a functor, could be expressed as regular functions operating on explicit first-class modules. It is my understanding (from the user land) that the module dependent capability will unlock the feasibility of an extension like this.

Why? First I think that'd be well inline with the pedagogical goals of the project.

But also, where sometimes you might not feel compelled to apply an entire functor just because you need one function, with a granularity of each function exposed with the explicit module, you may just start using them here and there.

I suspect this was your plan all along!

[gr-im]

That was our plan (The dissection of the modules was done to map naturally to Modular Implicit, by the way.), but now we don't put much effort into maintaining Preface :)
On the other hand, one obvious area for improvement would be to resolve the Traversable case, which requires the generation of functors to be functorialised and is elegantly solved by Modular Explicit.

[mbarbin]

Thank you for your reply. I like preface as a project to explore and help with propagating idioms. I learned already from limited studies on this repo and I'd like to pay it forward. Obviously if a stated goal is : "let's rewrite everything now" is unlikely to happen with a project that is not actively maintained, but on the other hand, if you create a space where contributor can incrementally contribute to translating "one module at a time" (is that realistic even?) then I am happy if you count me in the "nerd snipable pool".