| 08:26 | <canadahonk> | is there a spec reference for prefetch using Sec-Fetch-Dest: empty? (cc Noam Rosenthal)it makes sense (to me) but not sure if there's an explicit reference which should be used |
| 08:31 | <Noam Rosenthal> | canadahonk: yes! https://html.spec.whatwg.org/#link-type-prefetch:fetch-and-process-the-linked-resource (#3) |
| 08:32 | <canadahonk> | thanks! |
| 12:19 | <annevk> | Domenic: so when I click on any of the types/objects in https://webidl.spec.whatwg.org/#ArrayBufferView I end up in the same place as when I click those linked from https://webidl.spec.whatwg.org/#dfn-typed-array-type |
| 12:20 | <annevk> | Domenic: so at least fundamentally it seems like Web IDL treats them as interchangeable already |
| 12:22 | <annevk> | I guess I should leave that as a comment in the PR. Also found https://w3c.github.io/IndexedDB/#convert-value-to-key thanks to dontcallmedom |
| 12:28 | <Domenic> | annevk: yes. I don't think that changes my point that "typed array types" is a concept you reference when talking about types, whereas Uint8Array is a concept you reference when talking about either types or instances. |
| 12:30 | <Domenic> | We say "a Uint8Array" as a shorthand for "a Uint8Array instance", and we say "Uint8Array" as a shorthand for "the Uint8Array type". But we don't say "x is a typed array type" when x is an instance. We can say "x is a ArrayBufferView (instance)" if we want though. |
| 12:31 | <annevk> | Domenic: I'm pretty sure there's precedent for "x is A or B" and then using "x" in that sense, e.g., in DOM |
| 12:32 | <annevk> | Domenic: I guess you're saying there's some magic imbued by it being in Web IDL in this particular section, but that seems super weird |
| 12:32 | <Domenic> | I don't think there is when "A" or "B" have "type" in their <dfn> string. |
| 12:34 | <annevk> | Okay, so the magic is imbued by "type", that seems even worse, if we ever had MIMEType or equivalent |
| 12:35 | <annevk> | I don't mind upholding the fiction for now and no longer exporting these terms (apart from buffer source types they don't appear to be used elsewhere), but this doesn't seem like a tenable solution long term |
| 12:36 | <Domenic> | I don't think it's magic, it's just staying consistent with how Web IDL is defining terms. |
| 12:36 | <Domenic> | Like definitely if you're using "type" in some sense other than "type in a formal type system" (e.g., MIME type) then you don't need to follow this idea. |
| 12:37 | <Domenic> | ES has a similar distinction since it's also defining a formal type system |
| 12:38 | <Domenic> | https://tc39.es/ecma262/#sec-ecmascript-language-types-boolean-type vs. https://tc39.es/ecma262/#sec-terms-and-definitions-boolean-value |
| 12:39 | <Domenic> | and then informally "a Boolean" is shorthand for "a Boolean value", but you don't say "true is a Boolean type" |
| 12:56 | <annevk> | ES seems to have String vs String though, at least |
| 12:57 | <annevk> | or even String type vs String |
| 12:57 | <annevk> | And they're not saying "String type is a String" |
| 15:24 | <Ehsan Azari> | I should read spec, does it cover uniform array views? or just DataView which are slower than uniform array views (TypedArrayViews) Also covers other things like Float64Arrays |