Skip to content

Rename col! to column!. #19071

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

Merged
merged 1 commit into from
Nov 20, 2014
Merged

Rename col! to column!. #19071

merged 1 commit into from
Nov 20, 2014

Conversation

huonw
Copy link
Member

@huonw huonw commented Nov 18, 2014

This macro is very rarely used, so there is no need (and it is better)
for it to avoid the abbreviation.

Closes rust-lang/rfcs#467.

@@ -552,17 +552,17 @@ pub mod builtin {
/// A macro which expands to the column number on which it was invoked.
///
/// The expanded expression has type `uint`, and the returned column is not
/// the invocation of the `col!()` macro itself, but rather the first macro
/// the invocation of the `column!()` macro itself, but rather the first macro
/// invocation leading up to the invocation of the `col!()` macro.
Copy link
Contributor

Choose a reason for hiding this comment

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

what about !col here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Whoops, thanks.

This macro is very rarely used, so there is no need (and it is better)
for it to avoid the abbreviation.

Closes rust-lang/rfcs#467.

[breaking-change]
bors added a commit that referenced this pull request Nov 20, 2014
This macro is very rarely used, so there is no need (and it is better)
for it to avoid the abbreviation.

Closes rust-lang/rfcs#467.
@bors bors closed this Nov 20, 2014
@bors bors merged commit 3f3b2d6 into rust-lang:master Nov 20, 2014
lnicola pushed a commit to lnicola/rust that referenced this pull request Feb 10, 2025
…niquely

Previously it may have been possible for different completion items to
produce colliding hashes, not because of the hash but because of how
the items were serialized into byte streams for hashing. See rust-lang#19071
for details.

The chances of that happening were low, if it was actually possible at
all. Nevertheless, this commit ensures that it definitely can't happen.

This commit uses a handful of techniques used to fix this, but they all
boil down to "ensure this could be re-parsed". If it's possible to parse
to recreate the original item, then by construction there is no chance
of two different items getting serialized to identical byte streams.
lnicola added a commit to lnicola/rust that referenced this pull request Feb 10, 2025
Fix rust-lang#19071: ensure `completion_item_hash` serializes items uniquely
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.

Rename col! to column!
3 participants