Tensegritics / Tensegritics/ClojureDart
Catching incompatible classes before Dart does
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.6k
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
See #177 or https://clojurians.slack.com/archives/C03A6GE8D32/p1676766935857169
Even if deferecord was involved in both cases it can happen with any incompatible classes combination.
If we could catch it at the ClojureDart level rather than waiting for the Dart compiler to complain it would be a usability gain.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #177 and the linked Clojurians Slack discussion for the incompatible-class cases described there. Determine how ClojureDart could report these incompatibilities before the Dart compiler, with completion defined as catching the relevant class combinations at the ClojureDart level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, dart
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100