expand: Do not do questionable span adjustment before eagerly expanding an expression

Maybe it made sense when it was introduced, but now it's doing something incorrect.

Author: petrochenkov

src/libsyntax/ext/base.rs

@@ -908,12 +908,9 @@ impl<'a> ExtCtxt<'a> {
 /// compilation on error, merely emits a non-fatal error and returns `None`.
 pub fn expr_to_spanned_string<'a>(
     cx: &'a mut ExtCtxt<'_>,
-    mut expr: P<ast::Expr>,
+    expr: P<ast::Expr>,
     err_msg: &str,
 ) -> Result<(Symbol, ast::StrStyle, Span), Option<DiagnosticBuilder<'a>>> {
-    // Update `expr.span`'s ctxt now in case expr is an `include!` macro invocation.
-    expr.span = expr.span.apply_mark(cx.current_expansion.id);
-
     // Perform eager expansion on the expression.
     // We want to be able to handle e.g., `concat!("foo", "bar")`.
     let expr = cx.expander().fully_expand_fragment(AstFragment::Expr(expr)).make_expr();

src/test/ui/hygiene/eager-from-opaque.rs

@@ -1,6 +1,8 @@
 // Opaque macro can eagerly expand its input without breaking its resolution.
 // Regression test for issue #63685.
 
+// check-pass
+
 macro_rules! foo {
     () => {
         "foo"
@@ -9,7 +11,7 @@ macro_rules! foo {
 
 macro_rules! bar {
     () => {
-        foo!() //~ ERROR cannot find macro `foo!` in this scope
+        foo!()
     };
 }