tlaplus / tlaplus/CommunityModules
`Functions.tla` here clashes with `Functions.tla` in TLAPM
Nobody has claimed this yet.
- Dominant language
- TLA
- Stars
- 315
- Forks
- 48
- Avg merge
- 13h 27m
- Merged PRs (30d)
- 2
Description
There is a name clash between the Functions.tla in CommunityModules and Functions.tla in TLAPM, with the Functions.tla in CommunityModules (CM!Functions.tla) having a superset of operators compared to the version in TLAPM. Users who open specs that depend on CM!Functions.tla but who have PM!Functions.tla on the library path (first) end up with an unparsable spec.
/cc @muenchnerkindl @xxyzzn
Likely related: https://github.com/tlaplus/tlapm/issues/3
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
Compare CM!Functions.tla in CommunityModules with PM!Functions.tla in TLAPM, then reproduce the unparsable-spec failure with PM!Functions.tla first on the library path. Review the related TLAPM issue for context; done means resolving the name clash without losing the CommunityModules operators or breaking dependent specs.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100