Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / tc39/proposal-regexp-legacy-features issues and pull requests
#21 - Editorial: some document changes
Pull Request -
State: open - Opened by VoltrexKeyva about 1 year ago
#20 - Fix a typo
Pull Request -
State: closed - Opened by nico about 2 years ago
#19 - What should be the function name/toString() representation of the RegExp.$&, $+, $`, $' getters
Issue -
State: open - Opened by woess almost 4 years ago
- 3 comments
#18 - Editorial: Convert spec to ecmarkup
Pull Request -
State: open - Opened by ExE-Boss over 4 years ago
- 1 comment
#17 - Consider making `$`-prefixed getters `SameValue` with the equivalent non‑`$` getters
Issue -
State: open - Opened by ExE-Boss over 4 years ago
- 1 comment
#16 - fix three minor typos in markdown
Pull Request -
State: closed - Opened by bathos over 6 years ago
#15 - Write tests for test262
Issue -
State: open - Opened by leobalter over 7 years ago
- 2 comments
#14 - Update to stage 3
Pull Request -
State: closed - Opened by exarus over 7 years ago
- 1 comment
#13 - heading markup fix
Pull Request -
State: closed - Opened by dckc over 7 years ago
#12 - Missing RegExp.$*?
Issue -
State: closed - Opened by domenic over 8 years ago
- 1 comment
#11 - Would it be easier to store [[Realm]] instead of [[LegacyRegExpConstructor]]?
Issue -
State: closed - Opened by domenic over 8 years ago
- 3 comments
#10 - Convince browser vendors to implement this
Issue -
State: open - Opened by claudepache over 8 years ago
- 5 comments
#9 - Present as proposal to TC39
Issue -
State: closed - Opened by claudepache over 8 years ago
- 6 comments
#8 - Do not try to be too smart with RegExp static properties
Issue -
State: closed - Opened by claudepache over 8 years ago
#7 - Should the RegExp.$1 getter check the value of its this value?
Issue -
State: closed - Opened by claudepache over 8 years ago
- 2 comments
#6 - How to disable RegExp.$1, etc. for proper subclasses of RegExp
Issue -
State: closed - Opened by claudepache over 8 years ago
- 7 comments
#5 - Refactoring hazard when using legacy static RegExp methods in conjunction with instances of proper subclass of RegExp
Issue -
State: closed - Opened by claudepache almost 9 years ago
- 2 comments
#4 - This proposal needs to explicitly specify the right annex
Issue -
State: closed - Opened by erights almost 9 years ago
- 2 comments
#3 - Unsafe non-standard properties, like these, must be configurable and deletable
Issue -
State: closed - Opened by erights almost 9 years ago
- 8 comments
#2 - Should legacy RegExp features be disabled for subclasses and/or cross-realm?
Issue -
State: closed - Opened by claudepache about 9 years ago
- 4 comments
#1 - Should those properties be nonenumerable?
Issue -
State: closed - Opened by claudepache about 9 years ago
- 1 comment