-
Notifications
You must be signed in to change notification settings - Fork 427
Issues: chapel-lang/chapel
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Dyno: CI linters miss
contentsMatchInner bugs
area: BTR
area: Dyno
type: Bug
#27020
opened Mar 31, 2025 by
DanilaFe
[Bug]: when array element type omitted, compiler makes something up?
area: Compiler
area: Dyno
type: Bug
user issue
#26399
opened Dec 12, 2024 by
cassella
[Feature Request]: grepcomp should check all dyno locations, too
area: Dyno
type: Feature Request
#26278
opened Nov 20, 2024 by
lydia-duncan
Dyno: named declarations should report their indentation separately from their name locations
area: Dyno
#25208
opened Jun 10, 2024 by
DanilaFe
CLS: Enum values print as dyno ids instead of their name
area: Dyno
area: Python bindings
area: Tools
#25114
opened May 24, 2024 by
jabraham17
[Bug]: Type inlay hints are printed incorrectly for several types
area: Dyno
area: Python bindings
area: Tools
type: Bug
#25113
opened May 24, 2024 by
jabraham17
dyno: odd issue when calling
init without this
area: Dyno
type: Bug
#25053
opened May 15, 2024 by
DanilaFe
dyno: semantic checks in generic initializers are printed twice
area: Dyno
type: Bug
#24900
opened Apr 22, 2024 by
DanilaFe
dyno: should
nil and none have their own AST nodes?
area: Dyno
#24851
opened Apr 15, 2024 by
DanilaFe
dyno: expose a universal 'pretty print document' representation
area: Dyno
area: Tools
#24716
opened Mar 29, 2024 by
DanilaFe
parser: note the locations of all comments
area: Dyno
area: Tools
#24715
opened Mar 29, 2024 by
DanilaFe
dyno: support cascading forwarding statements
area: Dyno
type: Unimplemented Feature
#24709
opened Mar 28, 2024 by
DanilaFe
dyno: relying on
isQueryRunning in field genericity code seems incorrect
area: Dyno
#24105
opened Dec 18, 2023 by
DanilaFe
Seg fault when scope resolving
CommDiagnostics in a later generation
area: Dyno
type: Bug
#23943
opened Nov 29, 2023 by
jabraham17
dyno: generic type formals don't behave according to spec
area: Dyno
type: Bug
#23630
opened Oct 11, 2023 by
DanilaFe
improve stop-gap method resolution error
area: Compiler
area: Dyno
#23085
opened Aug 25, 2023 by
mppf
Attribute AST node locations aren't correctly computed
area: Dyno
type: Bug
#22931
opened Aug 9, 2023 by
DanilaFe
public use'ing a module that has public uses doesn't work as intended.
area: Compiler
area: Dyno
type: Bug
#22749
opened Jul 13, 2023 by
DanilaFe
Dyno: is it okay that named imports leak private information from the module they import from?
area: Dyno
type: Design
#22737
opened Jul 13, 2023 by
DanilaFe
Dyno: importing tertiary methods via a type name is unimplemented
area: Dyno
type: Bug
#22734
opened Jul 12, 2023 by
DanilaFe
Dyno: track original names of extern types in addition to their linkage names.
area: Dyno
type: Unimplemented Feature
#22711
opened Jul 11, 2023 by
DanilaFe
dyno: some classes are / will be resolved differently based on
--std
area: Dyno
type: Design
#22634
opened Jun 28, 2023 by
DanilaFe
dyno: separate compilation AST files ignored under --dyno due to path prefix differences
area: Dyno
type: Bug
#21973
opened Mar 27, 2023 by
DanilaFe
dyno: incorrect error reported for task private variables using loop indices
area: Dyno
type: Bug
#21972
opened Mar 27, 2023 by
DanilaFe
dyno: consider tracking type aliasing with QualifiedType
area: Dyno
type: Feature Request
#20914
opened Oct 25, 2022 by
DanilaFe
ProTip!
Updated in the last three days: updated:>2025-04-12.