David Montague

In general, I think it might be nice if `ValidationError` and/or `ErrorWrapper` was a little more extensible. I was thinking about this because of how surprisingly awkward it was to...

Just want to add some color on the issues with `typing.TypedDict`: Big picture, the issues stem from: 1, inheritance and the fact that you can't "walk" the base classes at...

Also, to be clear, we could have a ref present on both the ModelSchema _and_ the TypedDictSchema, but I think there is a benefit of keeping the CoreSchema refs we...

@samuelcolvin that doesn't expose a way to retrieve the errors afterward does it? I implemented a slight tweak to @adriangb's very good suggestion here: https://gist.github.com/dmontagu/7f0cef76e5e0e04198dd608ad7219573, this creates a type `LenientList`...

I'm not familiar with Microsoft KeyVault, but if it is what I would assume it is from the name, this seems like it might be a good candidate for a...

@alvarolopez the reason we introduced `computed_field` was so that properties _could_ be included in the serialization/output of `model_dump`. I'm curious — what is the use case you have in mind...

I think it makes sense in principle; in practice I'd rather not add more code to maintain without a good motivating reason :). Thanks for closing the issue.

@samuelcolvin Possibly related? https://github.com/pydantic/pydantic-core/issues/589

This would be pretty cool. Just curious — are you familiar with any other crates, or especially PyO3 projects, doing a JIT thing like this with rust? Also worth considering,...

If this is valid according to python typing (in particular, handled properly by `mypy`, `pyright`, etc.), then I think it may be possible to fix this issue by just converting...