Monica S.

I was thinking that the expression `a + b` would bind to `op_AdditionChecked`, `op_AdditionUnchecked` or `op_Addition` based on: - The presence (or lack thereof) of `op_AdditionChecked` and `op_AdditionUnchecked` - The...

> @FiniteReality > > > ... you can retain behavioural backwards compatibility with people who expect operator + to be checked ... > > If there was no way to...

Personally, I think `Color.Default` should be an uninitialized value, which we handle correctly in the API requests. This way, existing code assuming the correct behaviour does not need to be...

A simple solution which wouldn't require much effort would be to include a private bool member, which would default to false. Then, in a non-default ctor we'd initialize it to...

All of our Emote classes are in Core, since they're basically container types for data. Adding ModifyAsync/DeleteAsync would require a large breaking change to move them over into at least...

The runtime throws when it fails to load a DLL, the fact that it's in an unsafe class doesn't change anything. Something else is at fault here, most likely.

Does it happen outside of Docker? It may be a docker issue causing libs to load weirdly

If that's the case, it may be best for you to compile D.Net yourself and breakpoint the places where we call into libopus and libsodium, to step through and see...

Pretty sure we ended up deciding that interface additions weren't breaking version changes, due to the internal-implementation-only part of them. Overall, I'm not sure this is actually a worthwhile change...

Design discussion from dev server: - Current records don't have properties documented - Primary ctor was primarily for convenience w/ naming and ordering, since parameter name = property name -...