-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: layering on nonexistent objects #1560
Conversation
Deploying with Cloudflare Pages
|
± Registry diff
📊 PerformanceKeyNote that each bar component rounds up to the nearest 100ms, so each full bar is an overestimate by up to 400ms.
If a row has only one bar instead of four, that means it's not a trio and the bar just shows the total time spent for that example, again rounded up to the nearest 100ms. Data
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this bug and fixing it quickly!
Description
Resolves #1557 .
This PR fixes the bug of uncaught error when a
layer
directive is applied to nonexistent objects. As an example,The compiler doesn't check that
a
andb
actually exist, nor does it confirm that indeed,a
andb
are shapes.Implementation strategy and design decisions
When translating
layer
statements, the compiler now resolves each expression and ensures that each object exists and are ofShape
type. If not, it reports an error.Examples with steps to reproduce them
The Style code used in the example now properly reports an error when necessary.
Checklist