Curl Functionality about toaststunt HOT 3 CLOSED

Thank you for the feedback. While merging the functions is not impossible -- in fact, that indeed was the original idea -- for the very valid concern that it could and will present an issue with Toaststunt's current limitations, I would argue that doing so would actually reduce complexity and maintenance.
Such a function possessing numerous responsibilities would inherently become unwieldy, especially when you consider adding yet more behavior. Generally accepted design patterns encourage short -- focused functions in place of lengthy ones. Which is not to say there should never be exceptions, but rather to explain the thought-process behind it.
I do agree that space should be left in the implementation for eventually specifying protocol(HTTP, FTP, GOFER, IMAP... etc) and welcome more discussion on how we could make that a reality. Adding additional arguments? With all that above stated, I am open to discuss and adjust accordingly.
If you were curious where I drew my design concepts from: https://google.github.io/styleguide/cppguide.html

from toaststunt.

Merging these into a single builtin would be more ideal for reduction of complexity, maintenance, and the currently imposed function table limit. There are other options that we may want from curl in the future outside of HTTP methods as well; as such, I propose converting the second argument in the curl() builtin to an option map instead, where these changes to the behavior can be defined. include_headers can be folded into this second argument.

from toaststunt.

I was thinking the exact same thing as what @distantorigin has written. Single function with an options-map that resembles curl-parameters

from toaststunt.