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
  • #90
Closed
Open
Issue created Aug 29, 2013 by Tim Disney@disnetContributor

slowdown in resolve

The following is causing a pretty bad slowdown:

(function foo() {
    (function foo() {
        (function foo() {
            (function foo() {
                (function foo() {
                    (function foo() {
                        (function foo() {
                            (function foo() {
                                (function foo() {
                                    (function foo() {


                                    })
                                })
                            })
                        })
                    })
                })
            })
        })
    })
})

Same thing happens to nested macro definitions and identical vars being generated from a macro:

macro m {
    case {_ () } => { return #{var x;} }
}
m ()
m ()
m ()
m ()
...

The slowdown is taking place in resolve. Pretty sure this has to do with how we handle definition contexts.

Assignee
Assign to
Time tracking