Open Issues Need Help
View All on GitHubA collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: The EO parser needs to be updated to recognize the new notation introduced in EO language version 0.58.1. This update is essential for the linter functionality, as it currently fails to correctly process code written with the latest syntax.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: This GitHub issue proposes a new semantic rule for the `as` attribute in child objects. It states that if a parent object does not possess a `@base` attribute, none of its child objects should be permitted to use the `as` attribute. This distinction aims to differentiate between object 'formations' (definitions), where `as` in children is prohibited without a parent `@base`, and 'applications' (usages), where it is allowed.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: The issue highlights an illegal XMIR structure where a 'formation' object (an `<o>` tag lacking `@base`) incorrectly contains an 'anonymous object' (an `<o>` tag lacking `@name`). This configuration is currently permitted but must be prohibited, as formations are strictly required to contain only named objects. The severity is classified as an `ERROR`.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: Add command-line functionality to the existing Java linter package by creating a `Main.java` class. This will enable execution from the command line, producing warnings in a user-friendly format such as text, XML, or SARIF.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: Create a new linter for the EO language's XMIR intermediate representation that detects undefined objects and attributes referenced within an EO program. The linter should identify cases where objects or attributes are used without being properly defined within the current scope or imported packages, providing informative error messages.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes
AI Summary: Add a new linter to the existing EO program style checker (lints) that enforces the mandatory use of the `@as` attribute within `<o/>` elements nested inside `<o base="..">` elements in XMIR. This addresses issues related to ambiguity and maintainability in EO programs.
A collection of style checkers for XMIR: they don't predict runtime errors, but prevent compilation mistakes