feedback: consolidating API signatures for better flexibility and consistency

[skoshx]

What is the problem this feature would solve?

tldr;
signatures like Stream.encodeText and Stream.splitLines, are quite limiting, because it means that you can't add options like Stream.encodeText({ options }) without making a major version, and they're also somewhat confusing, where many times i've written Stream.encodeText() in a pipe and had some weird type errors. this small inconsistency, where some functions are like Stream.decodeText(encoding?), and others like Stream.decodeText creates a bit of confusion and i think v4 is the perfect time to consolidate

thoughts?

What is the feature you are proposing to solve the problem?

--

What alternatives have you considered?

--

[gcanti]

it means that you can't add options like Stream.encodeText({ options }) without making a major version

FWIW in Schema I am declaring functions even when they don't seem strictly necessary at the moment for this exact reason, it leaves room to add options in the future if needed