Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / abathur/sublimelpc issues and pull requests

#29 - hunt down scope issue

Issue - State: open - Opened by abathur about 7 years ago

#29 - hunt down scope issue

Issue - State: open - Opened by abathur about 7 years ago

#28 - initial Travis-CI integration

Issue - State: open - Opened by abathur over 9 years ago - 1 comment
Labels: enhancement, test

#28 - initial Travis-CI integration

Issue - State: open - Opened by abathur over 9 years ago - 1 comment
Labels: enhancement, test

#27 - Pass all existing syntax tests

Issue - State: open - Opened by abathur over 9 years ago
Labels: review, test

#27 - Pass all existing syntax tests

Issue - State: open - Opened by abathur over 9 years ago
Labels: review, test

#26 - less aggressive inline-closure-parameter (i.e., $1, $2...) matching

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#26 - less aggressive inline-closure-parameter (i.e., $1, $2...) matching

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#25 - match ... operator less aggressively

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#25 - match ... operator less aggressively

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#24 - Finish type union matching

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#24 - Finish type union matching

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#23 - special matching for 0 prepended to some numeric values in sprintf format strings

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#23 - special matching for 0 prepended to some numeric values in sprintf format strings

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#22 - Finish matching for single-quoted charstrings

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#21 - Rewrite inheritance/default-visibility modifier matching

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#20 - Support for doxygen (and similar) style comments

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#19 - recognize -> operator(s) for call_other, struct member

Issue - State: open - Opened by abathur over 9 years ago
Labels: match

#18 - Need a good/comprehensive test-case for multi-character single-quoted char strings.

Issue - State: open - Opened by abathur over 9 years ago
Labels: help wanted, test

#17 - Process "pending" scopes in test files

Issue - State: open - Opened by abathur over 9 years ago
Labels: review, test

#16 - Finish initial coverage of syntax_test_closures.c and syntax_test_types.c

Issue - State: open - Opened by abathur over 9 years ago - 1 comment
Labels: test

#15 - Naming some language features (particularly operators & punctuation)

Issue - State: open - Opened by abathur over 9 years ago
Labels: review

#14 - Check the order of punctuation scope parts

Issue - State: open - Opened by abathur over 9 years ago
Labels: review

#12 - Make sure all unnecessary C support is actually gone.

Issue - State: open - Opened by abathur over 9 years ago
Labels: help wanted, review

#11 - Support for mudlib-specific predefined constants?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#10 - Support for driver-predefined constants?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#9 - Support for mudlib-specific addon efuns?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#8 - Support for mudlib-specific simul_efuns?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#7 - Support for mudlib-specific applied functions?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#6 - Support for common/standard applied functions?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#5 - How should we prioritize resource use vs. marking invalid syntax cases?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#4 - Should LPC features/syntax from LP-family drivers (apart from LDMud) be supported?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#2 - Should scopes/language feature coverage be exhaustive, or minimalistic?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion

#1 - Should matching be liberal or opinionated?

Issue - State: open - Opened by abathur over 9 years ago
Labels: discussion