Skip to content

Conversation

@Byron
Copy link
Contributor

@Byron Byron commented May 8, 2015

It is used in the header! macro, which is exported as well.
If tm! is not exported, external clients cannot user otherwise
exported macros anymore who are dependent on tm!.

It is used in the `header!` macro, which is exported as well.
If `tm!` is not exported, external clients cannot user otherwise
exported macros anymore who are dependent on `tm!`.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 85.45% when pulling 9cda054 on Byron:master into 38f40c7 on hyperium:master.

@pyfisch
Copy link
Contributor

pyfisch commented May 8, 2015

Probably this should have a better name if it is exported.

@Byron
Copy link
Contributor Author

Byron commented May 8, 2015

Indeed, I just did a 'I need this real quick' PR and ignored the fact that I have no clue what it does. tm seems like too short for a rather global namespace without any hygiene.
I will leave the PR up anyway though, until the topic has received the attention it (probably) deserves.

@seanmonstar
Copy link
Member

I'm thinking along the lines of what I did for the mime! macro, until rust-lang/rust#25003 is fixed.

@seanmonstar
Copy link
Member

See #523

@Byron
Copy link
Contributor Author

Byron commented May 12, 2015

Thanks. The fix works for me.

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