Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

glimmerjs / glimmer-vm Public

Notifications You must be signed in to change notification settings
Fork 190
Star 1.1k

Code
Issues 99
Pull requests 57
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Correctly handle <:inverse> named block#1296

Merged

chancancode merged 2 commits intomasterglimmerjs/glimmer-vm:masterfrom fix-inverse-named-blockglimmerjs/glimmer-vm:fix-inverse-named-blockCopy head branch name to clipboard

Apr 20, 2021

Conversation Commits2 (2)Checks Files changed

Commits

Commits on Apr 20, 2021

Correctly handle <:inverse> named block
wagenet
committed
Warn when using both <:inverse> and <:else>
wagenet
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.