pydantic-core VS erg

Funny that you ask... https://github.com/pydantic/pydantic-core Unfortunately it seems that the functionality you ask for is not (yet) part of this ...

I encourage you to checkout the official benchmarks for more realistic and detailed examples, and, as always, YMMV.

> to also be constrained by a separate set of data types which are legal in rust.

This isn't really how writing rust/python iterop works. You tend to have opaque handles you call python methods on. Here's a decent example I found skimming the code.

https://github.com/pydantic/pydantic-core/blob/main/src/inpu...

Thanks for pointing out to that, I did not know about it. Also attaching repo in case someone would be interested as well - https://github.com/pydantic/pydantic-core

pydantic-core: The core validation logic for pydantic, a Python data parsing and validation library.

pydandic-core [0] will hopefully solve this issue (written in Rust)

[0] -- https://github.com/pydantic/pydantic-core

LinkedIn influencers are weird lol. Rust v Python is apples and oranges. Rust would be glued together by python just like it does with C/C++ and Java/Spark today. We’re already seeing some packages go this direction, like pydantic v2 is rewriting its core validation in rust.

Looking through the code, Pylyzer seems to be a thin wrapper around Erg [1]. To typecheck, it converts your Python AST to an Erg AST, then runs its through the Erg typechecker and returns the errors.

Faster typechecking for Python is very much needed. But this project seems like it was built in a hackathon —- it is not a true standalone typchecker.

[1] https://github.com/erg-lang/erg

erg – A Python-compatible statically typed language

I have been developing a programming language for a few years and this week I published it on GitHub.