Rethink unstable collection?

[jackfirth]

trafficstars

It's irritating to have to move things from unstable to stable when releasing, and it's difficult to organize the code when there's internals that unstable features depend on. It may be better to just put all features into the main collection and not provide them from lens, unstable/lens could just reprovide the unstable features itself. There'd only be one module in unstable, unstable/lens.rkt, and it'd be much easier to "turn on" new features for releases.

@AlexKnauth thoughts?

[AlexKnauth]

Do you mean add new features in lens/private/ but don't reprovide them from lens/main.rkt and have unstable/lens.rkt reprovide them instead? Yeah, that sounds like a much better idea.

[jackfirth]

Yes, that's exactly what I mean. Definitely seems more manageable.