Mitchell Hashimoto

@mwhooker Yeah it actually lets us add a lot. For example: https://github.com/hashicorp/logutils/blob/master/level.go I want to bring this into Packer at some point. So if we follow that structure it'll _just...

While you're changing API, can you change the returntype of the NEW function from `*map[string]Key` to `map[string]Key`. It doesn't make sense to return a pointer to that since maps are...

Looking back at this, I think we could consider adding an option to basically always deeply traverse `interface{}`. Mapstructure has always taken the approach where if direct assignment just works,...

Updating from the Ghostty side: we're not for sure certain Apple is aware of this or working on a fix. We're just _hoping_. But I am very confident it's a...

For Ghostty users, give the latest macOS build a shot and set the following config (new as of this comment): ``` window-vsync = true ``` After setting the config, fully...

So according to the HTTP spec (https://tools.ietf.org/html/rfc7230), the set of delimiters are simply not valid. I propose we accumulate an error but build-up as much of the header as we...

Actually, I may have misunderstood your issue initially. If the quoted name value isn't parsing colons properly then that would be a separate bug. I thought I tested that but...

Hm yes, this is intended and I think would be a breaking change to change the default. By decoding to a `map[string]interface{}` you are saying that the value `interface{}` is...

This looks good thanks! Apologies for the delay. :)

Hi! Hi @hovsater long time no see 😉 I'm working on fixing this for Ghostty as well and wanted to share some of my own research and discoveries that I...