Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A agnostic-lizard
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Michael Raskin
  • agnostic-lizard
  • Issues
  • #3

Closed
Open
Created Jan 30, 2022 by Michał Herda@mherda🤔

Top-level preservation: minor fix

https://gitlab.common-lisp.net/mraskin/agnostic-lizard/-/blob/master/doc/special-and-hardwired.txt#L15

Top-level preservation:

(...) return-from         No  
(...)                 

Nitpick: I don't think return-from can preserve toplevelness because a toplevel return-from is always an error because there is no block to return to.

Assignee
Assign to
Time tracking