| 17:40 | <shu> | bakkot: nice, structured headers landed. rebasing https://github.com/tc39/ecma262/pull/2442 right now and got a question |
| 17:41 | <shu> | the HostEnqueueFinalizationRegistryCleanupJob is structured a little oddly |
| 17:41 | <shu> | that's what it looks like on a local build |
| 17:42 | <shu> | the oddness is that the "Let cleanupJob be ..." section needs to come before the description that "[It] is an implementation-defined abstract operation that schedules [...]" |
| 17:43 | <shu> | this looks weird currently with an initial sentence "The abstract operation HostEnqueueFinalizationRegistryCleanupJob", then a bunch of stuff, then another sentence of "[It] is an impl-defined abstract operation" |
| 17:43 | <shu> | any thoughts on formatting this? |
| 17:44 | <shu> | my first thought was to rephrase the "is an implementation-defined abstraction operation that schedules [...]" sentence into a conformance requirement, but it's not really a conformance requirement |
| 17:50 | <shu> | hm, i think i will rephrase that sentence to "An implementation of HostEnqueueFinalizationRegistryCleanupJob schedules cleanupJob to be performed at some future time, if possible. It must also conform to the requirements in <emu-xref href="#sec-jobs"></emu-xref>" |
| 21:17 | <bakkot> | I like the phrasing it ended up as |