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.

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

[oxide] Expose experimental Rust parser setup #11116

Merged
merged 3 commits into from
Apr 27, 2023

Conversation

RobinMalfait
Copy link
Contributor

This PR introduces a new internal API that is only used for testing and benchmarking purposes. This
is not a public API and will be removed in the future.


Usage example:

import { parseCandidateStrings, IO, Parsing } from '@tailwindcss/oxide'

parseCandidateStrings(input, IO.Sequential | Parsing.Sequential)
parseCandidateStrings(input, IO.Sequential | Parsing.Parallel)
parseCandidateStrings(input, IO.Parallel | Parsing.Sequential)
parseCandidateStrings(input, IO.Parallel | Parsing.Parallel)

@RobinMalfait RobinMalfait changed the title [oxide] Improve Rust parser [oxide] Expose experimental Rust parser setup Apr 27, 2023
@RobinMalfait RobinMalfait merged commit e4a37ce into master Apr 27, 2023
21 checks passed
@RobinMalfait RobinMalfait deleted the feat/improve-rust-parser branch April 27, 2023 21:34
RobinMalfait added a commit that referenced this pull request May 12, 2023
* make `sequential` and `parallel` version of a new (tmp) `parse_candidate_strings`

* use bitmasks for the strategy

Only sending a number over the wire instead of a serialized objects.

* use cleaner match syntax
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.

None yet

1 participant