Conversation
Typealiases involving unsafe types that resolve to safe types should not be diagnosed.
…rd libraries Now that we aren't propagating "unsafe" to nested types, remove unnecessary "unsafe" keywords from the standard library.
…eir enclosing type When determining whether a nested type is safe, don't consider whether its enclosing type is safe. They're independent.
… types Use this to mark a few internal types @safe now that it works properly.
…as implicitly 'unsafe' This eliminates stray warnings.
…afe-fixes [Strict memory safety] Improve handling of safe types nested within unsafe ones
iMostfa
force-pushed
the
feature/generate-init-fix
branch
from
d24f2e4 to
7196ddc
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.