Closed BebeSparkelSparkel closed 7 months ago
I like LazyTextBuilder
since there is also type LazyText
, and so that leave room for TextBuilder
as the new (and public) name for StrictBuilder
.
I have added StrictTextBuilder
and LazyTextBuilder
.
I forgot we're already exporting StrictBuilder
. So LazyBuilder
for symmetry, instead of adding another step of renaming. Sorry for the confusion.
I can add LazyBuilder, but I want to have Text directly in the name with StrictTextBuilder and LazyTextBuilder to differentiate it from other builder types.
I want to have Text directly in the name with StrictTextBuilder and LazyTextBuilder to differentiate it from other builder types.
Wouldn't qualified imports let you disambiguate as well?
I see many type TextBuilder
aliases in packages so it seems that many people want to be able to disambiguate with the name.
https://github.com/search?q=%22type+TextBuilder%22+language%3AHaskell+&type=code
I forgot we're already exporting
StrictBuilder
. SoLazyBuilder
for symmetry, instead of adding another step of renaming. Sorry for the confusion.
We can go for StrictTextBuilder
/ LazyTextBuilder
and deprecate the existing StrictBuilder
name, I don't think there are any users at the moment.
That's fine by me, but let me defer the judgement to @Lysxia as an original author of StrictBuilder
.
Thanks!
Hmm, we have
StrictBuilder
already. Even while it's in an internal module and not widely advertised, it would be nice to come up with a consistent naming.Should this one be
LazyBuilder
orLazyTextBuilder
orTextLazyBuilder
?.. @Lysxia what do you think?