Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S sweet-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • sweet-js
  • sweet-core
  • Issues
  • #736
Closed
Open
Issue created Jul 17, 2017 by Tim Disney@disnetContributor

importing names that have been "marked" by macro expansion are being renamed

Importing names that have "gone through a macro" causes renaming in the import clause:

// mod.js
syntax m = ctx => {
  let first = ctx.next().value;
  let second = ctx.next().value;
  return #`class ${first} ${second}`;
}  
export m F { }

// main.js
import { F } from './mod.js';
let c = new F();

compiling main.js with sweet gives:

import {F_5} from "./mod.js";
let c_7 = new F_5;
Assignee
Assign to
Time tracking