Results 41 issues of arai-a

https://github.com/arai-a/ecma262-compare/runs/1895305028 > Site disk usage 11.5GB exceeds 10.0GB limit

backend

Post URL to ecma262 PR, after updating PR data

integration

* Only section title is changed (~~including the case only section number is changed~~ this case is fixed) * section has multiple paragraphs, or notes, and only some part is...

enhancement
UI

depends on https://github.com/arai-a/ecma262-compare/issues/14 Possible solutions: * Use `repository_dispatch` [1] , and directly trigger update from ecma262 repo * Use `issue_comment` [2] , and post issue comment from ecma262 repo *...

integration

It's not necessary to use the same repository for frontend and backend+history data if separating can solve the slow-deployment issue, it might be the way to go.

enhancement
backend

Test for https://github.com/tc39/ecma262/pull/2233

awaiting consensus

# Steps to reproduce: 1. run the following Python script and redirect the output to test.js ``` for i in range(1, 23): for j in range(0, int(1.7**i)): print '{};'.format(i) ```...

Just an idea for the next format. Currently prelude and content sections have multiple small streams (1 stream for each dictionary), and when decoding the file, decoder has to allocate...

currently `.grammar`, `.strings`, and `.tree` files are created by binjs_encode, which are I think only for debug purpose. so it should be created only if some parameter is specified.

Everything is inside history, we don't have to keep obsolete things in latest tree.

Bug: Tools