I encourage you to post a new package and invite pull requests. IMO little utility functions like these can be difficult to turn into worthwhile library functions, because they tend to be connected to particulars of the author's project design.
This is why, for instance, `pollen/unstable/typography` exists — those functions were good enough for me in my projects. But if they were going to be official library functions, they'd have to handle edge & corner cases better than they do. But, I make them available because for some people they may suffice, and others might use them to make better functions. So, even if consensus doesn't necessarily emerge, I think it's useful to have more sample code available for inspection. > On Apr 23, 2017, at 10:11 AM, Junsong Li <[email protected]> wrote: > > I am wondering can we build a collection of functions for common use? > > I am sure we all want something similar when processing document, like > generating URL, checking broken URL, extract headlines (sections), generates > notes on margins, etc. And I sometimes (or in most cases) just want to reuse > implementation from others instead of writing my own, especially in the > middle of writing :( > -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
