You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the C API, we want to use slices instead of locations in the
AST. In this case a "slice" is effectively the same thing as the
location, expect it is represented using a 32-bit offset and a
32-bit length. This will cut down on half of the space of all of
the locations in the AST.
Note that from the Ruby/Java/JavaScript side, this is effectively
an invisible change. This only impacts the C/Rust side.
Copy file name to clipboardExpand all lines: docs/configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ The available values for `type` are:
61
61
*`constant` - A field that is an integer that represents an index in the constant pool. This is a `pm_constant_id_t` in C.
62
62
*`constant[]` - A field that is an array of constants. This is a `pm_constant_id_list_t` in C.
63
63
*`location` - A field that is a location. This is a `pm_location_t` in C.
64
-
*`location?` - A field that is a location that is optionally present. This is a `pm_location_t` in C, but if the value is not present then the `start` and `end` fields will be `NULL`.
64
+
*`location?` - A field that is a location that is optionally present. This is a `pm_location_t` in C, but if the value is not present then the `length` field will be `0`.
65
65
*`uint8` - A field that is an 8-bit unsigned integer. This is a `uint8_t` in C.
66
66
*`uint32` - A field that is a 32-bit unsigned integer. This is a `uint32_t` in C.
0 commit comments