Skip to content

Scopes: Should VendorExtensionItem be preserved by tools? #264

Description

@rakudrama

There is no description of how VendorExtensionItem should be processed beyond parsing.

(This is not urgent for us at this time.)

The data model (e.g. Original Scope Record, Generated Range Record) does not have any fields to preserve extension items. I'm assuming that it is intended that extension items apply as attributes of the range or scope in which they occur. Is order important? Is order with respect to other items permitted to matter?

If a general purpose tool was to copy a source map by decoding to a Decoded Source Map Record, and then re-encoding the record, what happens to the extension items? If we were to merge two source maps and de-duplicate the common sources, how should the extension items of the duplicate Original Scope Records be merged?

If dart2wasm was to generate extension items, what are the expectations on how binaryen would process these items? We don't intend to use this feature for the initial dart2wasm / binaryen tool chain. I'm just using binaryen as an example of a more complex general purpose tool than copying a source map.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions