tc39 proposal-regexp-legacy-features issues

tc39 / proposal-regexp-legacy-features

Legacy static properties of the RegExp constructor in JavaScript

Creative Commons Zero v1.0 Universal

41 stars 13 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Editorial: some document changes

#21 VoltrexKeyva opened 10 months ago
0
Fix a typo

#20 nico closed 1 year ago
0
What should be the function name/toString() representation of the RegExp.$&, $+, $`, $' getters

#19 woess opened 3 years ago
3
Editorial: Convert spec to ecmarkup

#18 ExE-Boss opened 4 years ago
1
Consider making `$`-prefixed getters `SameValue` with the equivalent non‑`$` getters

#17 ExE-Boss opened 4 years ago
1
fix three minor typos in markdown

#16 bathos closed 5 years ago
0
Write tests for test262

#15 leobalter opened 7 years ago
2
Update to stage 3

#14 exarus closed 7 years ago
1
heading markup fix

#13 dckc closed 7 years ago
0
Missing RegExp.$*?

#12 domenic closed 8 years ago
1
Would it be easier to store [[Realm]] instead of [[LegacyRegExpConstructor]]?

#11 domenic closed 8 years ago
3
Convince browser vendors to implement this

#10 claudepache opened 8 years ago
5
Present as proposal to TC39

#9 claudepache closed 7 years ago
6
Do not try to be too smart with RegExp static properties

#8 claudepache closed 8 years ago
0
Should the RegExp.$1 getter check the value of its this value?

#7 claudepache closed 8 years ago
2
How to disable RegExp.$1, etc. for proper subclasses of RegExp

#6 claudepache closed 8 years ago
7
Refactoring hazard when using legacy static RegExp methods in conjunction with instances of proper subclass of RegExp

#5 claudepache closed 8 years ago
2
This proposal needs to explicitly specify the right annex

#4 erights closed 8 years ago
2
Unsafe non-standard properties, like these, must be configurable and deletable

#3 erights closed 8 years ago
8
Should legacy RegExp features be disabled for subclasses and/or cross-realm?

#2 claudepache closed 8 years ago
4
Should those properties be nonenumerable?

#1 claudepache closed 8 years ago
1