Jess 83e46b3728 LibRegex: Fix crash when parse result exceeds max cache size ...

Before, If the cache was empty we would try and evict non-existant
entries and crash. So the fix is to make sure that we don't saturate
the cache with a single parse result.

2025-04-04 16:10:25 +02:00

..

RegExp.escape.js

LibJS: Implement the RegExp.escape proposal

2024-12-05 13:56:21 +01:00

RegExp.js

LibRegex: Fix crash when parse result exceeds max cache size

2025-04-04 16:10:25 +02:00

RegExp.legacy.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.@@match.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.@@replace.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.compile.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.exec.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.flags.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.hasIndices.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.source.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.test.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00

RegExp.prototype.toString.js

Everywhere: Hoist the Libraries folder to the top-level

2024-11-10 12:50:45 +01:00