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

Linker improvements #6105

Closed
wants to merge 3 commits into from
Closed

Linker improvements #6105

wants to merge 3 commits into from

Conversation

Aatch
Copy link
Contributor

@Aatch Aatch commented Apr 29, 2013

Adds two extra flags: --linker which takes extra flags to pass to the linker, can be used multiple times and --print-link-args which prints out linker arguments. Currently --print-link-args needs execution to get past translation to get the LinkMeta data.

I haven't done tests or updated any extra documentation yet, so this pull request is currently here for review.

@Aatch
Copy link
Contributor Author

Aatch commented Apr 29, 2013

The motivation for this was a person on IRC (@ssbr) that was running into difficulties integrating rust into the distutils python build.

Other use cases are allowing for custom linker scripts and choosing libraries without encoding them into the crate itself.

@catamorphism
Copy link
Contributor

--print-link-args should be a -Z option, I think. I would be happier if --linker was something like --link-flag instead; --linker makes it seem like it's specifying the name of the linker executable to use.

Thanks!

@Aatch
Copy link
Contributor Author

Aatch commented Apr 30, 2013

I've changed the names of the flags. I'm also not sure how to test the change, any suggestions for starting points?

bors added a commit that referenced this pull request May 1, 2013
Adds two extra flags: `--linker` which takes extra flags to pass to the linker, can be used multiple times and `--print-link-args` which prints out linker arguments. Currently `--print-link-args` needs execution to get past translation to get the `LinkMeta` data.

I haven't done tests or updated any extra documentation yet, so this pull request is currently here for review.
@bors bors closed this May 1, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Oct 9, 2020
Lint for invisible Unicode characters other than ZWSP

This PR extends the existing `zero_width_space` lint to look for other invisible characters as well (in this case, `\\u{ad}` soft hyphen.

I feel like this lint is the logical place to add the check, but I also realize the lint name is not particularly flexible, but I also understand that it shouldn't be renamed for compatibility reasons.

Open questions:
 - What other characters should trigger the lint?
 - What should be done with the lint name?
 - How to indicate the change in functionality?

Motivation behind this PR: rust-lang#77417 - I managed to shoot myself in the foot by an invisible character pasted into my test case.

changelog: rename [`zero_width_space`] to [`invisible_characters`] and add SHY and WJ to the list.
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.

4 participants