Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note with explicit purpose of 1, 4, and 5 field segments #116

Merged
merged 2 commits into from
Jul 11, 2024
Merged

Add note with explicit purpose of 1, 4, and 5 field segments #116

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9048e89
Add note with explicit purpose of 1, 4, and 5 field segments
takikawa Jul 10, 2024
b3c3482
Merge branch 'main' into clarify-segment-semantics
jkup Jul 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion source-map.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,10 +250,14 @@ The fields in each segment are:
Note: The purpose of this encoding is to reduce the source map size. VLQ encoding reduced source maps by 50% relative to the [[V2Format]] in tests performed
using Google Calendar.

Note: Segments with one field are intended to represent generated code that is unmapped because there
is no corresponding original source code, such as code that is generated by a compiler. Segments
with four fields represent mapped code where a corresponding name does not exist. Segments with five
fields represent mapped code that also has a mapped name.

Note: Using file offsets was considered but rejected in favor of using line/column data to avoid becoming
misaligned with the original due to platform-specific line endings.


Resolving Sources {#resolving-sources}
--------------------------------------

Expand Down
Loading