098 2 和其他JIT的比较 我们知道有Numba, hope JIT, Graal Python, 但Restrain 是不同的。 我把Restrain的特性称为“CPython Compatible” Working With Existing And Prospective C-Extensions 兼容C extensions, 尽管不能优化, 但可以做到调用的开销尽可能接近CPython

runtime # Rust async runtime Analyze the reason of runtime isolation # Async runtime binding # Compatible layer 1 Create a wheel used everywhere Table of Contents 2 3 # Rust async runtime 1 Light-weight binding # Compatible layer 3 Insight of compatible layer • Rust lang and compiler → syntax and task type • Async compatible layer → I/O and task management Compatible layer Compatible Layer Compare • Tokio • Async-std • Similar component structures Compatible layer Compare runtimes • Tokio • Async-std • Almost the same APIs Compatible layer Main components in async runtimes • Macros •

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to change: • The recipes have to be updated to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. • The conan commands commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the more relevant changes. • General changes not related to the recipes nor the Conan commands, “build

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to change: • The recipes have to be updated to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. • The conan commands commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the more relevant changes. • General changes not related to the recipes nor the Conan commands, “build

expressions Using installed packages Using installed packages with mypy (PEP 561) Creating PEP 561 compatible packages Extending and integrating mypy Integrating mypy into another Python application Extending Check that functions don’t have empty bodies outside stubs [empty-body] Check that return value is compatible [return-value] Check types in assignment statement [assignment] Check that assignment target is __setattr__(self, name: str, value: int) -> None: ... # This will allow access to any A.x, if x is compatible with the return type def __getattr__(self, name: str) -> int: ... a = A() a.foo = 42 # Works

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. Please be aware that although the recipes can be compatible between and 2.0, the generated Conan binary packages won’t be compatible between versions. • The conan commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to change: • The recipes have to be updated to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. • The conan commands commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the more relevant changes. • General changes not related to the recipes nor the Conan commands, “build

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to change: • The recipes have to be updated to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. • The conan commands commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the more relevant changes. • General changes not related to the recipes nor the Conan commands, “build

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to change: • The recipes have to be updated to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. • The conan commands commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the more relevant changes. • General changes not related to the recipes nor the Conan commands, “build

necessary binaries for the current platform and configuration are downloaded, not all of them. If the compatible binary is not available, the package can be built from sources in the client too. 1.4 All platforms to be compatible with Conan 2.0. There are 2.0 features ported to Conan 1.X so you can get a compatible recipe with 2.0 using Conan 1.X. Please be aware that although the recipes can be compatible between and 2.0, the generated Conan binary packages won’t be compatible between versions. • The conan commands have also changed, but there are no “compatible” commands introduced in Conan 1.X. We will review the