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

Draft: Use @safe and @trusted #840

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

nordlow
Copy link
Contributor

@nordlow nordlow commented Aug 15, 2021

Depends on dlang-community/dsymbol#162.

Also inserts some @safe and @trusted mainly in dsymbol.

Using this in call to

make -f posix.mak style

in phobos passes without crash.

@nordlow nordlow changed the title Use @safe when possible Draft: Use @safe when possible Aug 15, 2021
@nordlow nordlow changed the title Draft: Use @safe when possible Draft: Use @safe and @trusted Aug 16, 2021
@nordlow nordlow changed the title Draft: Use @safe and @trusted Use @safe and @trusted Aug 22, 2021
@nordlow nordlow changed the title Use @safe and @trusted Use @safe and @trusted and replace Mallocator with GCAllocator #162 Aug 22, 2021
@nordlow nordlow changed the title Use @safe and @trusted and replace Mallocator with GCAllocator #162 Use @safe and @trusted and replace Mallocator with GCAllocator Aug 22, 2021
@nordlow nordlow changed the title Use @safe and @trusted and replace Mallocator with GCAllocator Replace Mallocator with GCAllocator to avoid crash when analyzing phobos Aug 22, 2021
@nordlow nordlow changed the title Replace Mallocator with GCAllocator to avoid crash when analyzing phobos Replace Mallocator with GCAllocator Aug 22, 2021
@nordlow nordlow changed the title Replace Mallocator with GCAllocator Use GCAllocator when possible to avoid crash when analyzing phobos Aug 22, 2021
{
}
else
int main(string[] args)
int main(string[] args) @trusted
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the point of this change?

Copy link
Member

Choose a reason for hiding this comment

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

shouldn't main be @safe instead of @trusted?

Copy link
Contributor

@RazvanN7 RazvanN7 left a comment

Choose a reason for hiding this comment

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

Unless I am missing something, this doesn't change the allocator at all. It simply adds safe and trusted.

@nordlow
Copy link
Contributor Author

nordlow commented Aug 23, 2021

Unless I am missing something, this doesn't change the allocator at all. It simply adds safe and trusted.

You're correct. I'll update the title.

@nordlow nordlow changed the title Use GCAllocator when possible to avoid crash when analyzing phobos Use @safe and @trusted Aug 23, 2021
@nordlow nordlow changed the title Use @safe and @trusted Use @safe and @trusted and bump dsymbol to avoid crash when analyzing phobos Aug 23, 2021
@@ -81,7 +81,7 @@ protected:
override void visit(const T structDec)
{
inAggregate = true;
structDec.accept(this);
() @trusted { structDec.accept(this); } ();
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this accept call can generally be @trusted, this should probably stay @system

{
}
else
int main(string[] args)
int main(string[] args) @trusted
Copy link
Member

Choose a reason for hiding this comment

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

shouldn't main be @safe instead of @trusted?

@nordlow nordlow changed the title Use @safe and @trusted and bump dsymbol to avoid crash when analyzing phobos Use @safe and @trusted Aug 25, 2021
@nordlow nordlow changed the title Use @safe and @trusted Draft: Use @safe and @trusted Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants