Le 2025-09-11 16:33, Vinnie Falco via Boost a écrit :
On the one hand, I think that exploring the API design space to improve and polish the interface for end users is great, so kudos for that.
However, this is exactly the sort of thing that could be done before the formal review by going out into the market and acquiring users with real-world use-cases and real-world problems who can provide the best possible feedback for changes. I think the model of writing a library direct-for-review works for certain authors (Joaquin with Bloom and Peter with Hash2 come to mind). Yet I do not think that it works in general. For example I always build up substantial users for my own libraries and the feedback ahead of the formal review has been pivotal in getting the libraries into shape. I would encourage this model going forward.
Isn't it exactly what the boost library incubator was designed for? Give visibility to a library, explicitly state it as experimental, so breakage and unstabilities are very likely to happen, and at some point when the author think it's ready, make a formal review. Why didn't it work like expected? Regards, Julien