Michael

Hi @bmorris3 ! Sorry for the late reaction. I recently reviewed the code. Unfortunately the suggested loop for trapz within the numba implementation assumes, that all the group members of...

I guess the cleanest way to do that, would be to hand that computed field on instantiating the class. Seems a bit out of scope.

Would be great to have that. This would also solve https://github.com/jcrist/msgspec/issues/425

@alexei I don't see your point. Sounds a bit like the linux command line philosophy, except it just doesn't make sense to apply it here. If you need validation without...

@davfsa If it's only about making the parsed objects more usable, what about simply: ```python class Foo(msgspec.Struct): version: int data: ... @property def options(self): return self.data.options ``` You might even...

@mjkanji What you could do is create tagged attribute objects. Then msgspec can distinguish them and you can add some verification. ```python class Attribute(msgspec.Struct, tag_field="Name") pass class Firstname(Attribute, tag="first_name"): Value:...

Hi @cutecutecat , if you don't care about further fields of "data" and "issues", just go with ordinary dictionaries and happily nest the type definition: ```python from typing import Literal...

Making `omit_defaults` and `repr_omit_defaults` inheritable might be an alternative to having it as `encode` option. Btw. `repr_omit_defaults` is currently implemented, but not yet documented.

@jcrist Oh, didn't see that. I was looking for it in the `Struct` doc here and there is no repr_omit_defaults: https://jcristharif.com/msgspec/structs.html

Thanks for the quick response, @goanpeca ! @dcherian was so kind, to fix our workflow using micromamba for now. I hope this issue report is still useful and updated the...