Skip to content

[internal] Different representation for unicode string and byte string in the lambda layer #1291

@bobzhang

Description

@bobzhang

To avoid we accidentialy optimize unicode string operations.
Note since we did validation that is valid utf8, so some string operations like (concat) are still valid, but String.length and String.get should be forbidden

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleOld issues that went stale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions