-
Notifications
You must be signed in to change notification settings - Fork 621
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
Add xeval #581
Add xeval #581
Conversation
1e152cd
to
185159d
Compare
It is embarrassing, but I have to admit I just spot a bug with the |
@kevinkassimo maybe it's worth fixing the problem in this PR? IMHO it makes sense to move |
2db97bc
to
ef76abf
Compare
@bartlomieju I had a PR fixing the behavior in the deno repo. I’ll wait for it to be reviewed and see we can completely move it here |
I was also thinking if we should move |
Co-authored-by: Nayeem Rahman <[email protected]>
Yes that makes sense, I'd also suggest adding |
Well it behaves like |
@Narendra-Kamath I like the idea of including Also we might want to distinguish Also I noticed https://github.com/denoland/deno_std/blob/master/io/readers.ts . We can maybe also implement a |
Yeah. Most accurately it reads, decodes to string and splits. |
👍 additionally Rust has As for the renaming of @nayeemrmn can you update the PR? There are a few issues waiting on this functionality :) |
@bartlomieju I think moving |
I'm fine with landing this first (as long as we don't expose |
@ry please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Nayeem Rahman <[email protected]> Original: denoland/std@a2cae36
Experimenting with moving
deno xeval
here.CC @bartlomieju @kevinkassimo