edfcore 0.4.346 → 0.4.348
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +29 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
|
|
|
109
109
|
readonly reserved: 224;
|
|
110
110
|
};
|
|
111
111
|
/** Published package version. Kept in sync with package.json by a test. */
|
|
112
|
-
export declare const VERSION = "0.4.
|
|
112
|
+
export declare const VERSION = "0.4.348";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,35 @@ alone does not tell you whether you were affected.
|
|
|
6
6
|
edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
|
|
7
7
|
defect; those are called out below.
|
|
8
8
|
|
|
9
|
+
## 0.4.348
|
|
10
|
+
|
|
11
|
+
- **Added** a check for what `index.locate` costs, against the two read counts `discontinuous.md`
|
|
12
|
+
prints — three for the first call, zero for a second one nearby.
|
|
13
|
+
- The zero is the one worth holding. A UI that calls `locate` on every pointer move is either free
|
|
14
|
+
or a request per frame, and nothing at the call site says which; a memo dropped in a refactor
|
|
15
|
+
changes no result at all, so no other test would notice. The three is worth holding for its
|
|
16
|
+
parenthesis rather than its size: records 0 and 5 are already known because `openEdf` probed
|
|
17
|
+
them, so the search starts from what the open already paid for.
|
|
18
|
+
- Also pinned: that the search reads one record at a time rather than widening to a range, which
|
|
19
|
+
would still answer correctly and cost far more over HTTP; and the file the page draws, whose span
|
|
20
|
+
of 16 and coverage of 6 are computed independently and differ by the ten seconds no record
|
|
21
|
+
covers.
|
|
22
|
+
|
|
23
|
+
## 0.4.347
|
|
24
|
+
|
|
25
|
+
- **Added** an execution of the `bigint` ticks decision on `design-decisions.md`. It is defended
|
|
26
|
+
with a specific, hard-to-notice failure — two onsets that are one instant on disk comparing
|
|
27
|
+
unequal after a round trip through a binary fraction, an averaging window landing a sample off
|
|
28
|
+
for a subset of trials — and that is arithmetic, so it can be shown instead of asserted.
|
|
29
|
+
- Worth showing, because the cost paragraph underneath is a standing invitation to convert to
|
|
30
|
+
seconds and be done with it. Three tenths is now demonstrated to be three times one tenth to the
|
|
31
|
+
tick and not in seconds, and a seven-decimal onset survives exactly while its float does not.
|
|
32
|
+
- The path itself is checked from the source. `tal/ticks.ts` states that `parseFloat`,
|
|
33
|
+
`Number(text)` and float arithmetic appear nowhere on it, and nothing made that true — it is one
|
|
34
|
+
careless conversion away from being false while every existing test passes, because the two agree
|
|
35
|
+
on almost every value. Scanned with comments stripped, since the docblock making the claim quotes
|
|
36
|
+
the very calls being looked for.
|
|
37
|
+
|
|
9
38
|
## 0.4.346
|
|
10
39
|
|
|
11
40
|
- **Added** an execution of the `strict` section of `design-decisions.md`, which is where the
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED