Matt Stancliff

> that's not a sensible solution to the problem. true, but the code still has to exist _somewhere_ (like the 5+ year bug example above... it was in the serialization...

yeah, [`BreakBeforeBraces: Attach`](https://clang.llvm.org/docs/ClangFormatStyleOptions.html#breakbeforebraces) looks correct. Removing any custom indent matching or function art is cleaner. Cleaning up inconsistencies looks good even if it changes some of the current style decisions...

> Can you apply it on a paragraph from inside your favorite editor? That's another approach reasonable too: only require formatting on updated things. the formatter can be made diff/patch-aware...

huh what now? no... let's do a list! - There's multiple things here (all unaddressed!) - please don't confuse community feedback with free work. I'm a customer paying a couple...

That's a great idea. Currently our API doesn't have a way to pass metadata for individual requests (which is a design flaw we need to fix eventually), so I'm not...

Oh, I wasn't questioning if they exist, was just wondering what they were. :) > I'd definitely want to help improve stripe-erlang where i can though, it'd make it easier...

It's a good idea. Right now our stripe-erlang library only supports one private token per application, so implementing stripe connect (and all the refactoring it will require) can open up...

I think there's a divide between two basic use cases which changes development priorities: - people who just want a cache and don't truly care about performance or implementation as...

Those are all logical steps. Very similar to when I worked out a multi-threaded archietcture a couple years ago: Be careful though because eventually you just end up implementing a...

> It's possible to avoid using IPs, by using hostnames instead. I'm not sure if there are any drawbacks. (Maybe some clients don't support hostnames.) Traditionally, redis has refused to...