Closed aheejin closed 6 months ago
I'm not strongly opinionated on the directory name either. The main reason I renamed it was in case there will be other proposals part of which may end up in this legacy
directory, it might be better if you conform to the original proposal names to prevent any confusion.... But I guess there will likely be no proposals going through a "journey" like this, after all? 🤷🏻
Will revert back to exceptions
for now then.
Yeah, I sincerely hope this doesn't become a regular thing. :) FWIW, I don't think proposal names are highly relevant for later spec matters, since they are historic and sometimes become inaccurate when a proposal evolves, see e.g. "bulk memory ops", "threads", etc.
This adds
core
andjs-api
directory indocument/legacy/exceptions
, moves all core spec files intocore/
, and restores the deleted legacy JS API files injs-api/
.The core legacy spec only contains the EH instructions, which is easier to view, but it is hard to precisely carve out the modified part from the JS API file, so this adds the whole file for the legacy spec.