Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Issue 23261 - druntime core.std.attribute.Tagged1_2 constructor i… #14771

Merged
merged 1 commit into from
Jan 6, 2023

Conversation

RazvanN7
Copy link
Contributor

@RazvanN7 RazvanN7 commented Jan 2, 2023

…s unsafe

@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @RazvanN7! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

  • My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
  • My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
  • I have provided a detailed rationale explaining my changes
  • New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.


If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Auto-close Bugzilla Severity Description
23261 normal druntime core.std.attribute.Tagged1_2 constructor is unsafe

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#14771"

@@ -236,9 +236,9 @@ version (UdaGNUAbiTag) struct gnuAbiTag
{
string[] tags;

this(string[] tags...)
this(string[] tags...) @safe
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
this(string[] tags...) @safe
this(string[] tags...) @safe pure nothrow

@RazvanN7
Copy link
Contributor Author

RazvanN7 commented Jan 3, 2023

@PetarKirov done.

@Geod24
Copy link
Member

Geod24 commented Jan 5, 2023

As mentioned in the issue, this code is only intended to be used as an UDA, so this issue doesn't make sense IMO.

@RazvanN7 RazvanN7 closed this Jan 5, 2023
@PetarKirov PetarKirov reopened this Jan 5, 2023
@PetarKirov
Copy link
Member

@Geod24 it's true that whether a problem exists at runtime or only theoretically at compile-time drastically changes the stakes. That said, I see no reason to keep an obviously unsafe code (even if the unsafety is theoretical) given how easy the fix is.

@RazvanN7 RazvanN7 merged commit 6711d9e into dlang:master Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants