Skip to content

Conversation

@shoujohnny
Copy link

The ^ operator is not used in Froglet, but is reserved for use in other Forge languages. If you meant exclusive-or, use the xor operator instead.

The -> operator is only used for field declaration in Froglet.

Used this format

added error messages to *, ^, ~, and &. 

also added a new error message for |.
changed error messages to format of:

The `&` operator is not used in Froglet, but is reserved for use in other Forge languages. If you meant intersection, use `and` or `&&` instead.
@shoujohnny shoujohnny changed the base branch from main to dev April 29, 2025 17:22
(when (eq? (nodeinfo-lang (node-info expr-node)) LANG_ID)
(define loc (nodeinfo-loc (node-info expr-node)))
(raise-bsl-relational-error "&" expr-node loc)))
(raise-bsl-relational-error "&" expr-node loc "The `&` operator is not used in Froglet, but is reserved for use in other Forge languages. If you meant intersection, use `and` or `&&` instead.")))
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"If you meant logical and..." (since intersection is not allowed, we don't want to bring that up)

(raise-bsl-relational-error "&" expr-node loc)))
(raise-bsl-relational-error "&" expr-node loc "The `&` operator is not used in Froglet, but is reserved for use in other Forge languages. If you meant intersection, use `and` or `&&` instead.")))

(define (check-node-expr-op-| expr-node node-type child-types)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirm this is being registered with the lang-specific error framework. ( The | character isn't an operator, it's a reserved token. ) This seems like something we might want to include in the parser errors, when we can make them.

(raise-bsl-relational-error-expr-args "&" expr-args loc)))
(raise-bsl-relational-error-expr-args "&" expr-args loc "The `&` operator is not used in Froglet, but is reserved for use in other Forge languages. If you meant intersection, use `and` or `&&` instead.")))

(define (check-args-node-expr-op-| expr-args info)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to comment for | case above.

updated error changes after review
Copy link
Author

@shoujohnny shoujohnny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adjusted error messages in response to feedback!

@tnelson tnelson changed the base branch from dev to feat_cores_sterling November 13, 2025 17:32
@tnelson
Copy link
Owner

tnelson commented Nov 13, 2025

Redirecting this to a feature branch so I can adjust error test cases without putting dev in a broken state.

@tnelson tnelson merged commit 9a4db84 into tnelson:feat_cores_sterling Nov 13, 2025
1 check failed
tnelson added a commit that referenced this pull request Nov 13, 2025
* fix: join parsing, regression test, note on 2nd issue

* add: semantics test

* add: tests, no-op change to parser for readability

* add: revisions to get core (strings, for the moment) to sterling

* fix: unsat but no core

* stop sending core in place of source

* Froglet Error Message Changes (#306)

* update: error messages

---------

Co-authored-by: shoujohnny <johnson_shou@brown.edu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants