Bump version to 0.0.1a18 #982
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlexWaygood
approved these changes
Aug 14, 2025
CHANGELOG.md
Outdated
Comment on lines
7
to
8
| - fix goto-definition on imports ([#19834](https://github.com/astral-sh/ruff/pull/19834)) | ||
| - support recursive type aliases ([#19805](https://github.com/astral-sh/ruff/pull/19805)) |
There was a problem hiding this comment.
Suggested change
| - fix goto-definition on imports ([#19834](https://github.com/astral-sh/ruff/pull/19834)) | |
| - support recursive type aliases ([#19805](https://github.com/astral-sh/ruff/pull/19805)) | |
| - Fix goto-definition on imports ([#19834](https://github.com/astral-sh/ruff/pull/19834)) | |
| - Support non-generic recursive type aliases that use [the `type` statement](https://docs.python.org/3/reference/simple_stmts.html#grammar-token-python-grammar-type_stmt) ([#19805](https://github.com/astral-sh/ruff/pull/19805)) |
I think this is an important distinction because (while it's a very important first step), we still don't support most recursive type aliases that users would have in their code. We don't yet support:
- generic recursive type aliases
- explicit recursive type aliases that use
typing.TypeAlias - explicit recursive type aliases that use
typing.TypeAliasType - implicit recursive type aliases
| - Remove `Type::Tuple` ([#19669](https://github.com/astral-sh/ruff/pull/19669)) | ||
| - Repurpose `FunctionType.into_bound_method_type` to return `BoundMethodType` ([#19793](https://github.com/astral-sh/ruff/pull/19793)) | ||
| - Short circuit `ReachabilityConstraints::analyze_single` for dynamic types ([#19867](https://github.com/astral-sh/ruff/pull/19867)) | ||
| - Use separate Rust types for bound and unbound type variables ([#19796](https://github.com/astral-sh/ruff/pull/19796)) |
There was a problem hiding this comment.
not a great description of the user-facing impact, but I'm not sure how to describe this better...
|
Thank you @AlexWaygood ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.