Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / datawire/quark issues and pull requests
#173 - Quark include doesn't correctly do path resolution
Issue -
State: open - Opened by kflynn over 8 years ago
Labels: bug
#173 - Quark include doesn't correctly do path resolution
Issue -
State: open - Opened by kflynn over 8 years ago
Labels: bug
#173 - Quark include doesn't correctly do path resolution
Issue -
State: open - Opened by kflynn over 8 years ago
Labels: bug
#168 - Non-unique package declarations produce incomprehensible error message
Issue -
State: open - Opened by kflynn over 8 years ago
#168 - Non-unique package declarations produce incomprehensible error message
Issue -
State: open - Opened by kflynn over 8 years ago
#168 - Non-unique package declarations produce incomprehensible error message
Issue -
State: open - Opened by kflynn over 8 years ago
#161 - Quark compiler must check signatures of overridden methods
Issue -
State: open - Opened by bozzzzo over 8 years ago
- 1 comment
Labels: bug
#161 - Quark compiler must check signatures of overridden methods
Issue -
State: open - Opened by bozzzzo over 8 years ago
- 1 comment
Labels: bug
#161 - Quark compiler must check signatures of overridden methods
Issue -
State: open - Opened by bozzzzo over 8 years ago
- 1 comment
Labels: bug
#161 - Quark compiler must check signatures of overridden methods
Issue -
State: open - Opened by bozzzzo over 8 years ago
- 1 comment
Labels: bug
#146 - Method and function expressions on classes (unbound methods)
Issue -
State: open - Opened by plombardi89 over 8 years ago
- 5 comments
#143 - Compiler Crashes when Using Generics
Issue -
State: open - Opened by plombardi89 over 8 years ago
- 1 comment
Labels: bug
#143 - Compiler Crashes when Using Generics
Issue -
State: open - Opened by plombardi89 over 8 years ago
- 1 comment
Labels: bug
#143 - Compiler Crashes when Using Generics
Issue -
State: open - Opened by plombardi89 over 8 years ago
- 1 comment
Labels: bug
#143 - Compiler Crashes when Using Generics
Issue -
State: open - Opened by plombardi89 over 8 years ago
- 1 comment
Labels: bug
#122 - Mixing up namespaces and classes crashes the compiler
Issue -
State: open - Opened by kflynn over 8 years ago
#122 - Mixing up namespaces and classes crashes the compiler
Issue -
State: open - Opened by kflynn over 8 years ago
#122 - Mixing up namespaces and classes crashes the compiler
Issue -
State: open - Opened by kflynn over 8 years ago
#122 - Mixing up namespaces and classes crashes the compiler
Issue -
State: open - Opened by kflynn over 8 years ago
#111 - Make the Quark compiler console output less noisy
Issue -
State: closed - Opened by brikelly over 8 years ago
- 1 comment
Labels: enhancement
#111 - Make the Quark compiler console output less noisy
Issue -
State: closed - Opened by brikelly over 8 years ago
- 1 comment
Labels: enhancement
#96 - Comparison == macro is stupid: Quark Integer division causes Java Compilation Failure
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#96 - Comparison == macro is stupid: Quark Integer division causes Java Compilation Failure
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#96 - Comparison == macro is stupid: Quark Integer division causes Java Compilation Failure
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#96 - Comparison == macro is stupid: Quark Integer division causes Java Compilation Failure
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#72 - Quark does not require a method to return
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 1 comment
#72 - Quark does not require a method to return
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 1 comment
#72 - Quark does not require a method to return
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 1 comment
#72 - Quark does not require a method to return
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 1 comment
#69 - User-defined macros evaluating to nothing in Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#69 - User-defined macros evaluating to nothing in Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#69 - User-defined macros evaluating to nothing in Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#69 - User-defined macros evaluating to nothing in Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#64 - Quark Compiler Exception (no matching method)
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 2 comments
#64 - Quark Compiler Exception (no matching method)
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 2 comments
#64 - Quark Compiler Exception (no matching method)
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 2 comments
#64 - Quark Compiler Exception (no matching method)
Issue -
State: closed - Opened by plombardi89 almost 9 years ago
- 2 comments
#63 - Quark should produce Java using most generic type for collections.
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#63 - Quark should produce Java using most generic type for collections.
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#63 - Quark should produce Java using most generic type for collections.
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#63 - Quark should produce Java using most generic type for collections.
Issue -
State: open - Opened by plombardi89 almost 9 years ago
#55 - Interface not resolving in generated Java code
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#54 - Quark should complain when you instantiate an abstract class
Issue -
State: open - Opened by janicedatawire almost 9 years ago
#39 - No way to remove elements from a map
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#39 - No way to remove elements from a map
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#39 - No way to remove elements from a map
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#39 - No way to remove elements from a map
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#38 - No way to remove elements from a list
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#38 - No way to remove elements from a list
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#38 - No way to remove elements from a list
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#38 - No way to remove elements from a list
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#28 - Quark backends sometimes don't handle multiple instances of a package correctly
Issue -
State: closed - Opened by ark3 almost 9 years ago
- 1 comment
#28 - Quark backends sometimes don't handle multiple instances of a package correctly
Issue -
State: closed - Opened by ark3 almost 9 years ago
- 1 comment
#28 - Quark backends sometimes don't handle multiple instances of a package correctly
Issue -
State: closed - Opened by ark3 almost 9 years ago
- 1 comment
#28 - Quark backends sometimes don't handle multiple instances of a package correctly
Issue -
State: closed - Opened by ark3 almost 9 years ago
- 1 comment
#25 - Declaring variables before they are used results in errors in the generated Python code
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#25 - Declaring variables before they are used results in errors in the generated Python code
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#25 - Declaring variables before they are used results in errors in the generated Python code
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#25 - Declaring variables before they are used results in errors in the generated Python code
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#22 - Quark compiles with package-internal references to package names but the resulting code doesn't work
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#22 - Quark compiles with package-internal references to package names but the resulting code doesn't work
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#22 - Quark compiles with package-internal references to package names but the resulting code doesn't work
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#22 - Quark compiles with package-internal references to package names but the resulting code doesn't work
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#21 - Java cannot find symbol, illegal start of type errors from Quark file that compiles and runs in Python and Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#21 - Java cannot find symbol, illegal start of type errors from Quark file that compiles and runs in Python and Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#21 - Java cannot find symbol, illegal start of type errors from Quark file that compiles and runs in Python and Javascript
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#18 - Trying to compile a quark file without the files for referenced packages crashes the compiler
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#18 - Trying to compile a quark file without the files for referenced packages crashes the compiler
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#18 - Trying to compile a quark file without the files for referenced packages crashes the compiler
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#18 - Trying to compile a quark file without the files for referenced packages crashes the compiler
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#15 - >=, =, <= comparison operations not defined for numbers
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#15 - >=, =, <= comparison operations not defined for numbers
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#15 - >=, =, <= comparison operations not defined for numbers
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#15 - >=, =, <= comparison operations not defined for numbers
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#14 - Default values are not checked against type declarations
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#14 - Default values are not checked against type declarations
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#14 - Default values are not checked against type declarations
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#14 - Default values are not checked against type declarations
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 1 comment
#6 - Compiler should catch name collision between package and file name
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#6 - Compiler should catch name collision between package and file name
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#6 - Compiler should catch name collision between package and file name
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments
#6 - Compiler should catch name collision between package and file name
Issue -
State: closed - Opened by janicedatawire almost 9 years ago
- 3 comments