profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tkellen/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

bocoup/jqfundamentals.com 183

jQuery Fundamentals

bocoup/deployment-workflow 90

Modern Web Deployment Workflow

bocoup/JSARToolkit-Wrapper 53

A simple JavaScript wrapper for allowing you to easily track Augmented Reality Markers in a video source and replace them with custom PNGs.

bocoup/d3-reuse-examples 40

Building reusable charts with d3.chart

bocoup/django_gmapsfield 40

A Google Maps field type for the django web framework

bocoup/mobilevis 28

MobileVis - a gallery of mobile data visualizations

ashleygwilliams/philosophy_club 25

in order to criticize, we must first understand.

bocoup/open-web-fundamentals 22

a celebration and exploration of the open web, for and by those interested in becoming responsible and informed web- makers and consumers

bocoup/grunt-init-chromeapp 21

grunt-init template for creating Chrome Apps

Pull request review commenttc39/ecma262

Editorial: refactor runtime MV and add/use RoundStringMVResult

 <h2>Syntax</h2>          <emu-clause id="sec-runtime-semantics-mv-s">           <h1>Runtime Semantics: MV</h1>-          <p>The conversion of a String to a Number value is similar overall to the determination of the Number value for a numeric literal (see <emu-xref href="#sec-literals-numeric-literals"></emu-xref>), but some of the details are different, so the process for converting a String numeric literal to a value of Number type is given here. This value is determined in two steps: first, a mathematical value (MV) is derived from the String numeric literal; second, this mathematical value is rounded as described below. The MV on any grammar symbol, not provided below, is the MV for that symbol defined in <emu-xref href="#sec-static-semantics-mv"></emu-xref>.</p>-          <ul>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: [empty]</emu-grammar> is 0.-            </li>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: StrWhiteSpace</emu-grammar> is 0.-            </li>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: StrWhiteSpace? StrNumericLiteral StrWhiteSpace?</emu-grammar> is the MV of |StrNumericLiteral|, no matter whether white space is present or not.-            </li>-            <li>-              The MV of <emu-grammar>StrDecimalLiteral ::: `-` StrUnsignedDecimalLiteral</emu-grammar> is the negative of the MV of |StrUnsignedDecimalLiteral|. (Note that if the MV of |StrUnsignedDecimalLiteral| is 0, the negative of this MV is also 0. The rounding rule described below handles the conversion of this signless mathematical zero to a floating-point *+0*<sub>𝔽</sub> or *-0*<sub>𝔽</sub> as appropriate.)-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `Infinity`</emu-grammar> is 10<sup>10000</sup> (a value so large that it will round to *+&infin;*<sub>𝔽</sub>).-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` DecimalDigits</emu-grammar> is the MV of the first |DecimalDigits| plus (the MV of the second |DecimalDigits| times 10<sup>-_n_</sup>), where _n_ is the number of code points in the second |DecimalDigits|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_</sup>, where _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` DecimalDigits ExponentPart</emu-grammar> is (the MV of the first |DecimalDigits| plus (the MV of the second |DecimalDigits| times 10<sup>-_n_</sup>)) times 10<sup>_e_</sup>, where _n_ is the number of code points in the second |DecimalDigits| and _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `.` DecimalDigits</emu-grammar> is the MV of |DecimalDigits| times 10<sup>-_n_</sup>, where _n_ is the number of code points in |DecimalDigits|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `.` DecimalDigits ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_ - _n_</sup>, where _n_ is the number of code points in |DecimalDigits| and _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_</sup>, where _e_ is the MV of |ExponentPart|.-            </li>-          </ul>-          <p>Once the exact MV for a String numeric literal has been determined, it is then rounded to a value of the Number type. If the MV is 0, then the rounded value is *+0*<sub>𝔽</sub> unless the first non white space code point in the String numeric literal is `-`, in which case the rounded value is *-0*<sub>𝔽</sub>. Otherwise, the rounded value must be the Number value for the MV (in the sense defined in <emu-xref href="#sec-ecmascript-language-types-number-type"></emu-xref>), unless the literal includes a |StrUnsignedDecimalLiteral| and the literal has more than 20 significant digits, in which case the Number value may be either the Number value for the MV of a literal produced by replacing each significant digit after the 20th with a 0 digit or the Number value for the MV of a literal produced by replacing each significant digit after the 20th with a 0 digit and then incrementing the literal at the 20th digit position. A digit is significant if it is not part of an |ExponentPart| and</p>-          <ul>-            <li>-              it is not `0`; or-            </li>-            <li>-              there is a non-zero digit to its left and there is a non-zero digit, not in the |ExponentPart|, to its right.-            </li>-          </ul>+          <p>The conversion of a String to a Number value is similar overall to the determination of the Number value for a numeric literal (see <emu-xref href="#sec-literals-numeric-literals"></emu-xref>), but some of the details are different, so the process for converting a String numeric literal to a value of Number type is given here. Additional definitions for MV are provided in <emu-xref href="#sec-static-semantics-mv"></emu-xref>.</p>+          <emu-grammar>StringNumericLiteral ::: [empty]</emu-grammar>+          <emu-grammar>StringNumericLiteral ::: StrWhiteSpace</emu-grammar>+          <emu-alg>+            1. Return *+0*<sub>𝔽</sub>.+          </emu-alg>+          <emu-grammar>StringNumericLiteral ::: StrWhiteSpace? StrNumericLiteral StrWhiteSpace?</emu-grammar>+          <emu-alg>+            1. Return 𝔽(MV of |StrNumericLiteral|).+          </emu-alg>+          <emu-grammar>StrDecimalLiteral ::: `-` StrUnsignedDecimalLiteral</emu-grammar>+          <emu-alg>+            1. Let _a_ be MV of |StrUnsignedDecimalLiteral|.+            1. If _a_ is 0, return *-0*<sub>𝔽</sub>.+            1. Return RoundStringMVResult(-1 &times; _a_).

second seems most straightforward to me

michaelficarra

comment created time in 3 hours

Pull request review commenttc39/ecma262

Editorial: refactor runtime MV and add/use RoundStringMVResult

 <h2>Syntax</h2>          <emu-clause id="sec-runtime-semantics-mv-s">           <h1>Runtime Semantics: MV</h1>-          <p>The conversion of a String to a Number value is similar overall to the determination of the Number value for a numeric literal (see <emu-xref href="#sec-literals-numeric-literals"></emu-xref>), but some of the details are different, so the process for converting a String numeric literal to a value of Number type is given here. This value is determined in two steps: first, a mathematical value (MV) is derived from the String numeric literal; second, this mathematical value is rounded as described below. The MV on any grammar symbol, not provided below, is the MV for that symbol defined in <emu-xref href="#sec-static-semantics-mv"></emu-xref>.</p>-          <ul>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: [empty]</emu-grammar> is 0.-            </li>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: StrWhiteSpace</emu-grammar> is 0.-            </li>-            <li>-              The MV of <emu-grammar>StringNumericLiteral ::: StrWhiteSpace? StrNumericLiteral StrWhiteSpace?</emu-grammar> is the MV of |StrNumericLiteral|, no matter whether white space is present or not.-            </li>-            <li>-              The MV of <emu-grammar>StrDecimalLiteral ::: `-` StrUnsignedDecimalLiteral</emu-grammar> is the negative of the MV of |StrUnsignedDecimalLiteral|. (Note that if the MV of |StrUnsignedDecimalLiteral| is 0, the negative of this MV is also 0. The rounding rule described below handles the conversion of this signless mathematical zero to a floating-point *+0*<sub>𝔽</sub> or *-0*<sub>𝔽</sub> as appropriate.)-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `Infinity`</emu-grammar> is 10<sup>10000</sup> (a value so large that it will round to *+&infin;*<sub>𝔽</sub>).-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` DecimalDigits</emu-grammar> is the MV of the first |DecimalDigits| plus (the MV of the second |DecimalDigits| times 10<sup>-_n_</sup>), where _n_ is the number of code points in the second |DecimalDigits|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_</sup>, where _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits `.` DecimalDigits ExponentPart</emu-grammar> is (the MV of the first |DecimalDigits| plus (the MV of the second |DecimalDigits| times 10<sup>-_n_</sup>)) times 10<sup>_e_</sup>, where _n_ is the number of code points in the second |DecimalDigits| and _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `.` DecimalDigits</emu-grammar> is the MV of |DecimalDigits| times 10<sup>-_n_</sup>, where _n_ is the number of code points in |DecimalDigits|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: `.` DecimalDigits ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_ - _n_</sup>, where _n_ is the number of code points in |DecimalDigits| and _e_ is the MV of |ExponentPart|.-            </li>-            <li>-              The MV of <emu-grammar>StrUnsignedDecimalLiteral ::: DecimalDigits ExponentPart</emu-grammar> is the MV of |DecimalDigits| times 10<sup>_e_</sup>, where _e_ is the MV of |ExponentPart|.-            </li>-          </ul>-          <p>Once the exact MV for a String numeric literal has been determined, it is then rounded to a value of the Number type. If the MV is 0, then the rounded value is *+0*<sub>𝔽</sub> unless the first non white space code point in the String numeric literal is `-`, in which case the rounded value is *-0*<sub>𝔽</sub>. Otherwise, the rounded value must be the Number value for the MV (in the sense defined in <emu-xref href="#sec-ecmascript-language-types-number-type"></emu-xref>), unless the literal includes a |StrUnsignedDecimalLiteral| and the literal has more than 20 significant digits, in which case the Number value may be either the Number value for the MV of a literal produced by replacing each significant digit after the 20th with a 0 digit or the Number value for the MV of a literal produced by replacing each significant digit after the 20th with a 0 digit and then incrementing the literal at the 20th digit position. A digit is significant if it is not part of an |ExponentPart| and</p>-          <ul>-            <li>-              it is not `0`; or-            </li>-            <li>-              there is a non-zero digit to its left and there is a non-zero digit, not in the |ExponentPart|, to its right.-            </li>-          </ul>+          <p>The conversion of a String to a Number value is similar overall to the determination of the Number value for a numeric literal (see <emu-xref href="#sec-literals-numeric-literals"></emu-xref>), but some of the details are different, so the process for converting a String numeric literal to a value of Number type is given here. Additional definitions for MV are provided in <emu-xref href="#sec-static-semantics-mv"></emu-xref>.</p>+          <emu-grammar>StringNumericLiteral ::: [empty]</emu-grammar>+          <emu-grammar>StringNumericLiteral ::: StrWhiteSpace</emu-grammar>+          <emu-alg>+            1. Return *+0*<sub>𝔽</sub>.+          </emu-alg>+          <emu-grammar>StringNumericLiteral ::: StrWhiteSpace? StrNumericLiteral StrWhiteSpace?</emu-grammar>+          <emu-alg>+            1. Return 𝔽(MV of |StrNumericLiteral|).+          </emu-alg>+          <emu-grammar>StrDecimalLiteral ::: `-` StrUnsignedDecimalLiteral</emu-grammar>+          <emu-alg>+            1. Let _a_ be MV of |StrUnsignedDecimalLiteral|.+            1. If _a_ is 0, return *-0*<sub>𝔽</sub>.+            1. Return RoundStringMVResult(-1 &times; _a_).

We could also do this:

            1. Return RoundStringMVResult(0 - _a_).

Or this:

            1. Return RoundStringMVResult(-_a_).
michaelficarra

comment created time in 3 hours

Pull request review commenttc39/ecma262

Normative: Make B.1 "Additional Syntax" normative

 <h2>Syntax</h2>       SingleLineComment ::         `//` SingleLineCommentChars? +      SingleLineHTMLOpenComment ::+        `&lt;!--` SingleLineCommentChars?++      SingleLineHTMLCloseComment ::+        LineTerminatorSequence HTMLCloseComment++      HTMLCloseComment ::+        WhiteSpaceSequence? SingleLineDelimitedCommentSequence? `--&gt;` SingleLineCommentChars?++      SingleLineDelimitedCommentSequence ::+        SingleLineDelimitedComment WhiteSpaceSequence? SingleLineDelimitedCommentSequence?++      WhiteSpaceSequence ::+        WhiteSpace WhiteSpaceSequence?+       SingleLineCommentChars ::         SingleLineCommentChar SingleLineCommentChars?        SingleLineCommentChar ::         SourceCharacter but not LineTerminator++      SingleLineDelimitedComment ::+        `/*` SingleLineDelimitedCommentChars? `*/`++      SingleLineDelimitedCommentChars ::+        SingleLineNotAsteriskChar SingleLineDelimitedCommentChars?+        `*` SingleLinePostAsteriskCommentChars?++      SingleLineNotAsteriskChar ::+        SourceCharacter but not one of `*` or LineTerminator++      SingleLinePostAsteriskCommentChars ::+        SingleLineNotForwardSlashOrAsteriskChar SingleLineDelimitedCommentChars?+        `*` SingleLinePostAsteriskCommentChars?++      SingleLineNotForwardSlashOrAsteriskChar ::+        SourceCharacter but not one of `/` or `*` or LineTerminator     </emu-grammar>-    <p>A number of productions in this section are given alternative definitions in section <emu-xref href="#sec-html-like-comments"></emu-xref></p>++    <emu-clause id="sec-comments-early-errors">+      <h1>Static Semantics: Early Errors</h1>+      <emu-grammar>+        SingleLineHTMLOpenComment ::+          `&lt;!--` SingleLineCommentChars?++        HTMLCloseComment ::+          WhiteSpaceSequence? SingleLineDelimitedCommentSequence? `--&gt;` SingleLineCommentChars?+      </emu-grammar>+      <ul>+        <li>It is a Syntax Error if a |Module| contains the source code matching this production.</li>+      </ul>+      <emu-note>In a |Script|, this syntax is allowed, but deprecated.</emu-note>

It would be nice to clarify in https://tc39.es/ecma262/#sec-syntactic-and-lexical-grammars that "deprecated/legacy" means "optional for implementation".

It doesn't mean that. See here for a pending definition of "legacy".

However, I am in line with @jmdyck about putting deprecated behavior under something like if HostImplementsOptional() instead, but without "units" for now.

That suggestion is for when you take stuff from Annex B and incorporate it into the main spec, keeping it normative-optional. This PR (and #1867) take stuff from Annex B and incorporate it into the main spec, but make it normative.

jmdyck

comment created time in 5 hours

delete branch bocoup/aria-practices

delete branch : dependabot/npm_and_yarn/cspell-5.6.3

delete time in 9 hours

PR closed bocoup/aria-practices

Bump cspell from 4.1.5 to 5.6.3 dependencies javascript

Bumps cspell from 4.1.5 to 5.6.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/streetsidesoftware/cspell/blob/main/CHANGELOG.md">cspell's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.2...v5.6.3">5.6.3</a> (2021-06-11)</h2> <h3>Bug Fixes</h3> <ul> <li>fix issue with legacy dictionaries that do not have some accents (<a href="https://github.com/streetsidesoftware/cspell/commit/5a9aa27decba013299111a66a89da18c7123b321">5a9aa27</a>)</li> <li>make sure cspell-tools does not collide with old version. (<a href="https://github.com/streetsidesoftware/cspell/commit/00e360c03fe81d398944dd13a36e1fffac57250e">00e360c</a>)</li> <li>support case sensitive document checking. (<a href="https://github.com/streetsidesoftware/cspell/commit/527de4a80dd281526783404127d23a0b7a51ec52">527de4a</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.1...v5.6.2">5.6.2</a> (2021-06-10)</h2> <h3>Bug Fixes</h3> <ul> <li><em>minor breaking</em> fix issues with accents and the word splitter (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1330">#1330</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/845c3146efa8d4cce7bfdfbf76627ced298ac8b7">845c314</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.0...v5.6.1">5.6.1</a> (2021-06-09)</h2> <h3>Bug Fixes</h3> <ul> <li>Fix issues with accent characters (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1322">#1322</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/4d65dfbc3c0091450de2d6023b41c623faf763f0">4d65dfb</a>), closes <a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1321">#1321</a></li> <li>Use a dictionary for ignoreWords to be consistent with <code>words</code> (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1326">#1326</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/ee3897d62dcc5f5af177141734015ad9a9dcddff">ee3897d</a>)</li> </ul> <h1><a href="https://github.com/streetsidesoftware/cspell/compare/v5.5.2...v5.6.0">5.6.0</a> (2021-06-05)</h1> <h3>Features</h3> <ul> <li>support <code>.pnp.js</code> when loading configurations. (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1307">#1307</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/76da68cf6a13586598689d01bce3a24bc255530a">76da68c</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.5.1...v5.5.2">5.5.2</a> (2021-05-30)</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/streetsidesoftware/cspell/commit/6c1211a6af23fe4a4b5caa2d3029cdb2dbbde0fd"><code>6c1211a</code></a> v5.6.3</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/295c7857cb3b0c8c8c1721adf6e09523008a5281"><code>295c785</code></a> test: fix cspell-tools test</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/527de4a80dd281526783404127d23a0b7a51ec52"><code>527de4a</code></a> fix: support case sensitive document checking.</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/5a9aa27decba013299111a66a89da18c7123b321"><code>5a9aa27</code></a> fix: fix issue with legacy dictionaries that do not have some accents</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/00e360c03fe81d398944dd13a36e1fffac57250e"><code>00e360c</code></a> fix: make sure cspell-tools does not collide with old version.</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/640e8245373c83f0db8cf9aea813d20d77d0a31a"><code>640e824</code></a> ci: do not build integration test package on install</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/8cb8a3c612923451b6638f626f6fb9066bfa3625"><code>8cb8a3c</code></a> Update package.json</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/695965487e2bb7dcc3d5e6189153f3c2b678b247"><code>6959654</code></a> ci: Workflow Bot -- Update ALL Dependencies (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1333">#1333</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/9b2fcd5a6d80325683cfd479a071eb37b1445cf6"><code>9b2fcd5</code></a> v5.6.2</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/60ab2f7fb80725ebdbd1eb7e145633f6786729bb"><code>60ab2f7</code></a> ci: Workflow Bot -- Update ALL Dependencies (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1331">#1331</a>)</li> <li>Additional commits viewable in <a href="https://github.com/streetsidesoftware/cspell/compare/cspell@4.1.5...v5.6.3">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+451 -407

1 comment

2 changed files

dependabot[bot]

pr closed time in 9 hours

pull request commentbocoup/aria-practices

Bump cspell from 4.1.5 to 5.6.3

Superseded by #145.

dependabot[bot]

comment created time in 9 hours

create barnchbocoup/aria-practices

branch : dependabot/npm_and_yarn/cspell-5.6.4

created branch time in 9 hours

PR opened bocoup/aria-practices

Bump cspell from 4.1.5 to 5.6.4

Bumps cspell from 4.1.5 to 5.6.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/streetsidesoftware/cspell/blob/main/CHANGELOG.md">cspell's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.3...v5.6.4">5.6.4</a> (2021-06-15)</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1336">#1336</a> (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1342">#1342</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/7a0b278f5d96c163b901afeb3ef08f55af609dda">7a0b278</a>)</li> <li>early out on checking binary files. (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1337">#1337</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/a9488080daf99ed992ac55e450d522a78e5708d7">a948808</a>)</li> <li>Fix issue with missing suggestions (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1339">#1339</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/cfecde85b80d70063aa647d0f6837c879a938ce1">cfecde8</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.2...v5.6.3">5.6.3</a> (2021-06-11)</h2> <h3>Bug Fixes</h3> <ul> <li>fix issue with legacy dictionaries that do not have some accents (<a href="https://github.com/streetsidesoftware/cspell/commit/5a9aa27decba013299111a66a89da18c7123b321">5a9aa27</a>)</li> <li>make sure cspell-tools does not collide with old version. (<a href="https://github.com/streetsidesoftware/cspell/commit/00e360c03fe81d398944dd13a36e1fffac57250e">00e360c</a>)</li> <li>support case sensitive document checking. (<a href="https://github.com/streetsidesoftware/cspell/commit/527de4a80dd281526783404127d23a0b7a51ec52">527de4a</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.1...v5.6.2">5.6.2</a> (2021-06-10)</h2> <h3>Bug Fixes</h3> <ul> <li><em>minor breaking</em> fix issues with accents and the word splitter (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1330">#1330</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/845c3146efa8d4cce7bfdfbf76627ced298ac8b7">845c314</a>)</li> </ul> <h2><a href="https://github.com/streetsidesoftware/cspell/compare/v5.6.0...v5.6.1">5.6.1</a> (2021-06-09)</h2> <h3>Bug Fixes</h3> <ul> <li>Fix issues with accent characters (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1322">#1322</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/4d65dfbc3c0091450de2d6023b41c623faf763f0">4d65dfb</a>), closes <a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1321">#1321</a></li> <li>Use a dictionary for ignoreWords to be consistent with <code>words</code> (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1326">#1326</a>) (<a href="https://github.com/streetsidesoftware/cspell/commit/ee3897d62dcc5f5af177141734015ad9a9dcddff">ee3897d</a>)</li> </ul> <h1><a href="https://github.com/streetsidesoftware/cspell/compare/v5.5.2...v5.6.0">5.6.0</a> (2021-06-05)</h1> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/streetsidesoftware/cspell/commit/1bfcbb4fa1893378f54e6d7f1000ca1e79163170"><code>1bfcbb4</code></a> v5.6.4</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/fb396292ee5d6f24f9ff80f38ff67955a6744b38"><code>fb39629</code></a> ci: Workflow Bot -- Update ALL Dependencies (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1343">#1343</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/7a0b278f5d96c163b901afeb3ef08f55af609dda"><code>7a0b278</code></a> fix: <a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1336">#1336</a> (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1342">#1342</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/a4f448d5e4370f777c31483de5ad2e215a335d3d"><code>a4f448d</code></a> build(deps): bump streetsidesoftware/cspell-action from 1.2.2 to 1.2.4 (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1341">#1341</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/64a66a9367e2c0360ae052a31e059ad585483f5e"><code>64a66a9</code></a> ci: Workflow Bot -- Update ALL Dependencies (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1338">#1338</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/cfecde85b80d70063aa647d0f6837c879a938ce1"><code>cfecde8</code></a> fix: Fix issue with missing suggestions (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1339">#1339</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/a9488080daf99ed992ac55e450d522a78e5708d7"><code>a948808</code></a> fix: early out on checking binary files. (<a href="https://github-redirect.dependabot.com/streetsidesoftware/cspell/issues/1337">#1337</a>)</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/4ebb29e59fd109411b6d31ad38524330897fda77"><code>4ebb29e</code></a> ci: Workflow Bot -- Update ALL Dependencies</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/6c1211a6af23fe4a4b5caa2d3029cdb2dbbde0fd"><code>6c1211a</code></a> v5.6.3</li> <li><a href="https://github.com/streetsidesoftware/cspell/commit/295c7857cb3b0c8c8c1721adf6e09523008a5281"><code>295c785</code></a> test: fix cspell-tools test</li> <li>Additional commits viewable in <a href="https://github.com/streetsidesoftware/cspell/compare/cspell@4.1.5...v5.6.4">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+452 -407

0 comment

2 changed files

pr created time in 9 hours

Pull request review commenttc39/ecma262

Normative: Make B.1 "Additional Syntax" normative

 <h2>Syntax</h2>       SingleLineComment ::         `//` SingleLineCommentChars? +      SingleLineHTMLOpenComment ::+        `&lt;!--` SingleLineCommentChars?++      SingleLineHTMLCloseComment ::+        LineTerminatorSequence HTMLCloseComment++      HTMLCloseComment ::+        WhiteSpaceSequence? SingleLineDelimitedCommentSequence? `--&gt;` SingleLineCommentChars?++      SingleLineDelimitedCommentSequence ::+        SingleLineDelimitedComment WhiteSpaceSequence? SingleLineDelimitedCommentSequence?++      WhiteSpaceSequence ::+        WhiteSpace WhiteSpaceSequence?+       SingleLineCommentChars ::         SingleLineCommentChar SingleLineCommentChars?        SingleLineCommentChar ::         SourceCharacter but not LineTerminator++      SingleLineDelimitedComment ::+        `/*` SingleLineDelimitedCommentChars? `*/`++      SingleLineDelimitedCommentChars ::+        SingleLineNotAsteriskChar SingleLineDelimitedCommentChars?+        `*` SingleLinePostAsteriskCommentChars?++      SingleLineNotAsteriskChar ::+        SourceCharacter but not one of `*` or LineTerminator++      SingleLinePostAsteriskCommentChars ::+        SingleLineNotForwardSlashOrAsteriskChar SingleLineDelimitedCommentChars?+        `*` SingleLinePostAsteriskCommentChars?++      SingleLineNotForwardSlashOrAsteriskChar ::+        SourceCharacter but not one of `/` or `*` or LineTerminator     </emu-grammar>-    <p>A number of productions in this section are given alternative definitions in section <emu-xref href="#sec-html-like-comments"></emu-xref></p>++    <emu-clause id="sec-comments-early-errors">+      <h1>Static Semantics: Early Errors</h1>+      <emu-grammar>+        SingleLineHTMLOpenComment ::+          `&lt;!--` SingleLineCommentChars?++        HTMLCloseComment ::+          WhiteSpaceSequence? SingleLineDelimitedCommentSequence? `--&gt;` SingleLineCommentChars?+      </emu-grammar>+      <ul>+        <li>It is a Syntax Error if a |Module| contains the source code matching this production.</li>+      </ul>+      <emu-note>In a |Script|, this syntax is allowed, but deprecated.</emu-note>

It would be nice to clarify in https://tc39.es/ecma262/#sec-syntactic-and-lexical-grammars that "deprecated/legacy" means "optional for implementation".

However, I am in line with @jmdyck about putting deprecated behavior under something like if HostImplementsOptional() instead, but without "units" for now.

jmdyck

comment created time in 11 hours

push eventtc39/ecma262

bterlson

commit sha 41b89738db422d97ff364cc403f55f07fd3ca2bc

Update gh-pages [skip ci]

view details

push time in 13 hours

PR merged tc39/ecma262

Meta: CONTRIBUTING.md: Some changes to make the doc more beginner-friendly meta ready to merge

Editorial changes

  • Differentiate "Issue" (uppercase, as in the GitHub concept) from "issue" (lowercase, the problem). Same for "Pull Request".
  • Link the mailing list.
  • Minor word changes.

Layout and markup

  • Use code font for file names and branch names (Are you considering switching from master to main?).
  • Add new line after headings.
+14 -7

2 comments

1 changed file

tomayac

pr closed time in 13 hours

push eventtc39/ecma262

Thomas Steiner

commit sha 61cc3297c96764a256b02b90005550607371a1d1

Meta: CONTRIBUTING.md: Some changes to make the doc more beginner-friendly (#2431) - Add new line after headings - Link the discourse - Minor word changes

view details

push time in 13 hours

Pull request review commenttc39/ecma262

Editorial: Clarify and expand the discussion of terminal symbols

 <h1>The Syntactic Grammar</h1>      <emu-clause id="sec-grammar-notation" namespace="grammar-notation">       <h1>Grammar Notation</h1>-      <p>Terminal symbols are shown in `fixed width` font, both in the productions of the grammars and throughout this specification whenever the text directly refers to such a terminal symbol. These are to appear in a script exactly as written. All terminal symbol code points specified in this way are to be understood as the appropriate Unicode code points from the Basic Latin range, as opposed to any similar-looking code points from other Unicode ranges. A code point in a terminal symbol cannot be expressed by a `\\` |UnicodeEscapeSequence|.</p>-      <p>Nonterminal symbols are shown in <i>italic</i> type. The definition of a nonterminal (also called a &ldquo;production&rdquo;) is introduced by the name of the nonterminal being defined followed by one or more colons. (The number of colons indicates to which grammar the production belongs.) One or more alternative right-hand sides for the nonterminal then follow on succeeding lines. For example, the syntactic definition:</p>+      <p>The nonterminal symbols of all the ECMAScript grammars are shown in <i>italic</i> type.</p>+      <p>In all the grammars, 'verbatim' terminal symbols are shown in `fixed-width` font. These are to appear in a source text exactly as written. All terminal symbol code points specified in this way are to be understood as the appropriate Unicode code points from the Basic Latin range, as opposed to any similar-looking code points from other Unicode ranges. A code point in a terminal symbol cannot be expressed by a `\\` |UnicodeEscapeSequence|.</p>+      <p>In grammars whose terminal symbols are individual Unicode code points (i.e., the lexical, RegExp, and numeric string grammars), a contiguous run of multiple fixed-width code points appearing in a production is a simple shorthand for the same sequence of code points, written as standalone terminal symbols.</p>+      <p>For example, the production:</p>+      <emu-grammar type="example">+        HexIntegerLiteral :: `0x` HexDigits+      </emu-grammar>+      <p>is a shorthand for:</p>+      <emu-grammar type="example">+        HexIntegerLiteral :: `0` `x` HexDigits+      </emu-grammar>+      <p>In contrast, in the syntactic grammar, a contiguous run of fixed-width code points is a single terminal symbol.</p>+      <p>Terminal symbols come in two other forms:</p>+      <ul>+        <li>In the lexical and RegExp grammars, Unicode code points without a conventional printed representation are instead shown in the form "&lt;ABBREV&gt;" where "ABBREV" is a mnemonic for the code point. These forms are defined in <emu-xref href="#sec-unicode-format-control-characters" title></emu-xref> and <emu-xref href="#sec-white-space" title></emu-xref>.</li>+        <li>In the syntactic grammar, certain terminal symbols (e.g. |IdentifierName| and |RegularExpressionLiteral|) are shown in italics, as they refer to the nonterminals of the same name in the lexical grammar.</li>+      </ul>+      <p>The definition of a nonterminal (also called a &ldquo;production&rdquo;) is introduced by the name of the nonterminal being defined followed by one or more colons. (The number of colons indicates to which grammar the production belongs.) One or more alternative right-hand sides for the nonterminal then follow on succeeding lines. For example, the syntactic definition:</p>

@michaelficarra: Done

jmdyck

comment created time in 14 hours

pull request commenttc39/ecma262

Editorial: Clarify and expand the discussion of terminal symbols

force-pushed to rebase to master, resolve conflicts, and reword things slightly.

jmdyck

comment created time in 14 hours

pull request commenttc39/ecma262

Normative: Make B.1 "Additional Syntax" normative

force-pushed to:

  • drop the 2 commits that are covered by PR #1867
  • rebase to master, resolving conflicts and dropping 4 commits re fixing Annex A (since master already has the fixes)
jmdyck

comment created time in 16 hours

issue commentbocoup/test262-report-issue-tracker

Unexplained regression in JavaScriptCore results

This appears to have been caused by a change in eshost, a utility which this project depends on transitively through test262-harness.

I've filed a pull request to address the problem. If/when that is merged and released, the results collection process will automatically receive the new version, and the subsequently-collected JavaScriptCore results should be more authentic.

jugglinmike

comment created time in 18 hours

create barnchbocoup/eshost

branch : jsc-agent

created branch time in 18 hours

create barnchbocoup/eshost

branch : ci-test-jsc

created branch time in 18 hours

push eventtc39/dataset

github-actions[bot]

commit sha 85eac5ad15f35e29f58e17a1f78559d87daa6368

deploy: f6ad2bb19b6e75214377eae636c477d02837b13c

view details

push time in 19 hours

Pull request review commenttc39/ecma262

Editorial: Define + use StringToNumber, and better define NumericValue

 <h2>Syntax</h2>        <emu-clause id="sec-static-semantics-mv">         <h1>Static Semantics: MV</h1>-        <p>A numeric literal stands for a value of the Number type or the BigInt type.</p>+        <p>A numeric literal stands for a value of the Number type or the BigInt type, as specified by the syntax-directed operation NumericValue. Determining this value involves deriving a mathematical value (MV) from the literal, according to the following rules.</p>

I guess that's fair. In that case, I've opened #2435 where, among other things, I've gotten rid of these usages.

jmdyck

comment created time in 19 hours

issue openedbocoup/test262-report-issue-tracker

Unexplained regression in JavaScriptCore results

In recent (as of 2021-06-14) results published to test262.report, some of the data for JavaScriptCore appears to be inaccurate.

For example, the test at built-ins/Atomics/wait/nan-for-timeout.js passed on 2021-05-17 but failed on 2021-06-10. We're told that the JSC maintainers did not modify the implementation of Atomics during this period, and the test continues to report as "passing" in the project's own continuous integration environment.

This suggests that there is a flaw in the test262.report results collection mechanism.

created time in 20 hours

push eventtc39/ecma262

Michael Ficarra

commit sha a8f20fb2b1058e339b1f08a6894ee0436b2ee269

fix linting error

view details

push time in 20 hours

pull request commenttc39/ecma262

Editorial: refactor runtime MV and add/use RoundStringMVResult

Note that this races with #1554.

michaelficarra

comment created time in 21 hours

PR opened tc39/ecma262

Editorial: refactor runtime MV and add/use RoundStringMVResult editorial change
+58 -59

0 comment

1 changed file

pr created time in a day

create barnchtc39/ecma262

branch : mv

created branch time in a day

push eventtc39/how-we-work

Derek Lewis

commit sha 9fdae80e9f10a880587d4a58d3e04deb918bc5a1

fix incorrect & normalize matrix channel links to be human-readable

view details

Derek Lewis

commit sha e62bba5cfeb412ccfe763bfd69442648026aeade

restore `/#` component to matrix.to urls The #/ component is mandatory and exists to avoid leaking the target URL to the server hosting matrix.to. Refs: https://github.com/matrix-org/matrix.to/blob/3738594fbcf37ec3bc7da86cf2a1d1196a083609/README.md#url-scheme

view details

Ujjwal Sharma

commit sha 48a5481f342b3a7a1ed9e5d57835e3c545280004

Merge pull request #92 from DerekNonGeneric/fix/matrix-chan-links fix incorrect & normalize matrix channel links to be human-readable

view details

push time in a day

PR merged tc39/how-we-work

fix incorrect & normalize matrix channel links to be human-readable

Before this change, the links for…

  • #tc39-implementers
  • #tc39-ecma402
  • #tc39-website

… were all pointing to the same place (https://matrix.to/#/!hmsRHUEXriRovkvcin:matrix.org).

We appear to have missed this when we reviewed this part of the guide the other day (https://github.com/tc39/how-we-work/pull/89).

I am not entirely sure what that URL is to, but it seems like it could be to the whole TC39 Matrix “Space”?

While doing this, I found out that there is a way to make the links to these channels human-readable. The advantage to this is that the names of the rooms are populated with their actual names (as opposed to a random character sequence) while the element invitation page is loading.

It seems like these shareable Matrix links can be acquired via https://matrix.to/ w/o needing room invitation privileges, however, I was not able to figure out how to generate a human-readable shareable link to the entire space, which should probably be linked to separately (there does not seem to be a section of the guide expanding upon the “spaces” concept).

/cc @ryzokuken

+8 -8

6 comments

1 changed file

DerekNonGeneric

pr closed time in a day

pull request commenttc39/how-we-work

fix incorrect & normalize matrix channel links to be human-readable

The advantage to this is that the names of the rooms are populated with their actual names (as opposed to a random character sequence) while the element invitation page is loading.

I must've missed this. It does seem important and useful.

Thanks for the PR!

DerekNonGeneric

comment created time in a day

issue commenttc39/proposal-async-iteration

Where should value unwrapping be performed?

I've also hit this a couple times 😄

zenparsing

comment created time in a day

issue commenttc39/proposal-async-iteration

Where should value unwrapping be performed?

@erights a user (on Stack Overflow) was surprised that the values of promises were unwrapped when a regular iterable is passed i.e.:

(async () => {
  for await (const foo of [Promise.resolve(1), Promise.resolve(2)]) {
    console.log(foo); // user expected this to be a promise and for it to not "synchronize"
  }
})();
zenparsing

comment created time in a day