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

[1.38] Regression: cannot find macro trace! in this scope #63888

Closed
petrochenkov opened this issue Aug 25, 2019 · 2 comments
Closed

[1.38] Regression: cannot find macro trace! in this scope #63888

petrochenkov opened this issue Aug 25, 2019 · 2 comments
Assignees
Labels
P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Milestone

Comments

@petrochenkov
Copy link
Contributor

#63628 (comment)

cannot find macro trace! in this scope

cannot find macro flatdata_intersperse! in this scope

./reg/eztrace/0.1.0/beta-2019-08-13.txt:[INFO] [stderr] error: cannot find macro `trace!` in this scope

./reg/flatdata/0.3.0/beta-2019-08-13.txt:[INFO] [stderr] error: cannot find macro `flatdata_intersperse!` in this scope

Regression from #63114, fixed in #63717.
(The fix still needs a backport to beta.)

@petrochenkov petrochenkov added regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Aug 25, 2019
@nikomatsakis nikomatsakis added the P-high High priority label Aug 29, 2019
@nikomatsakis
Copy link
Contributor

Needs to be closed once #63717 is backported

@Mark-Simulacrum Mark-Simulacrum added this to the 1.38 milestone Aug 30, 2019
@pnkfelix
Copy link
Member

Closing as fixed since #63717 was backported to beta in rollup PR #64097

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants