-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
Conversation
|
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 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
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#14771" |
druntime/src/core/attribute.d
Outdated
| @@ -236,9 +236,9 @@ version (UdaGNUAbiTag) struct gnuAbiTag | |||
| { | |||
| string[] tags; | |||
|
|
|||
| this(string[] tags...) | |||
| this(string[] tags...) @safe | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| this(string[] tags...) @safe | |
| this(string[] tags...) @safe pure nothrow |
|
@PetarKirov done. |
|
As mentioned in the issue, this code is only intended to be used as an UDA, so this issue doesn't make sense IMO. |
|
@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. |
…s unsafe