Can proper Result/Option types be created for Go now?
replyYou can do pipelined option/result manipulation now, but without sum types/pattern matching it's not going to be quite as useful as Rust's.
replyNeat, stealing this.
replyI wrote a blog on it if you're interested: https://xeoncross.com/2026/better_go_handlers.html
replyThanks for the link, looks like a very pleasant framework to use! I was interested to see "Mid-fasthttp" on the slower end in the benchmarks at the bottom, do you know why that is?
replyBtw, the Gin and Echo examples reference an "input" variable but it doesn't seem to be defined there? Maybe it was intentional, since the examples are just to give a general idea of how the handler looks in each library, but thought I would let you know just in case it wasn't.
Due to the fact that fasthttp is not net/http compatible it is due to the conversion being required from a https://pkg.go.dev/net/http#Handler. It was included for information purposes as I though someone would be curious.
reply