Skip to content

Conversation

owenv
Copy link
Contributor

@owenv owenv commented Jul 28, 2023

Custom task data is often unstructured, and won't be valid UTF-8. Exposing API that works with data instead of strings avoids the need for hacks like base-64 encoding when creating them using the Swift API, and makes it easier to avoid UTF8 encoding overhead.

Also, adopt the use of a Swift user module version in llbuild, allowing clients to more easily stage in use of new API

rdar://112936539

…f strings

Custom task data is often unstructured, and won't be valid UTF-8. Exposing API that works with data instead of strings avoids the need for hacks like base-64 encoding when creating them using the Swift API, and makes it easier to avoid UTF8 encodign overhead.
@owenv
Copy link
Contributor Author

owenv commented Jul 28, 2023

@swift-ci please test

@owenv
Copy link
Contributor Author

owenv commented Jul 28, 2023

@swift-ci please smoke test

@owenv owenv merged commit 24237d0 into swiftlang:main Jul 28, 2023
@owenv owenv deleted the pr/ovoorhees/optimize-custom-tasks branch July 28, 2023 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants