StudioInfinity/dyna3
2
0
Fork 2
Code Issues 86 Pull requests 1 Projects 2 Releases 4 Wiki Activity Actions

Correct the argument-count error messages for Sphere and Point descriptors #156

New issue
Closed
opened 2026-06-12 22:29:03 +00:00 by Vectornaut · 3 comments
Vectornaut commented 2026-06-12 22:29:03 +00:00
Member
Copy link

As of pull request #155, we return an interpretation error when a Sphere or Point descriptor is given arguments, instead of just ignoring the extra arguments. The error message shouldn't describe Sphere and Point as regulators.

As of pull request #155, we return an interpretation error when a `Sphere` or `Point` descriptor is given arguments, instead of just ignoring the extra arguments. The error message shouldn't describe `Sphere` and `Point` as regulators.
glen commented 2026-06-12 22:43:57 +00:00
Owner
Copy link

Why don't you just push a commit to #155 fixing this since it is not merged yet? Thanks.

Why don't you just push a commit to #155 fixing this since it is not merged yet? Thanks.
Vectornaut commented 2026-06-12 22:59:28 +00:00
Author
Member
Copy link

Just posted a comment on pull request #155 to explain this! I'm happy to address this in #155, but it will increase the chances of a regression in the next pull request a little bit.

Just posted a [comment](pulls/155#issuecomment-3976) on pull request #155 to explain this! I'm happy to address this in #155, but it will increase the chances of a regression in the next pull request a little bit.
Vectornaut commented 2026-06-15 03:52:16 +00:00
Author
Member
Copy link

As requested, I've updated pull request #155 to correct this problem, so it should never arise on the main branch. When I rebased the next pull request, I managed to get a clean enough diff to be confident it won't lead to a regression.

As [requested](pulls/155#issuecomment-3983), I've updated pull request #155 to correct this problem, so it should never arise on the main branch. When I rebased the next pull request, I managed to get a clean enough diff to be confident it won't lead to a regression.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
readme-toplevel
kaleidocycle-example
outline-update-fix
lang-trials
seed-problem
demo-summer-2025_update
0.3pre
0.2
v0.1.1
v0.1.0
Labels
Clear labels   
bug
Something is not working

  
ci
Issue concerning the continuous integration system

  
design
Issue that entails architecture/design decisions

  
duplicate
This issue or pull request already exists

  
engine
Issue concerning the engine

  
enhancement
New feature

  
maintenance
Refactors andother behavior-orthogonal tasks

  
prospective
This will become an issue once a particular feature is implemented or pull request is merged

  
question
More information is needed

  
regression
A bug that's resurfaced or a feature that's accidentally been removed

  
stub
We need to fill in the details of this issue

  
todo
Planned step in implementation

  
ui
Issue concerning the user interface

  
wontfix
This won't be fixed

No labels
bug
ci
design
duplicate
engine
enhancement
maintenance
prospective
question
regression
stub
todo
ui
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
StudioInfinity/dyna3#156
No description provided.