We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
get-bytevector-n! and get-string-n! both have end instead of count as argument, which is also reflected in that they do the wrong thing.
get-bytevector-n!
get-string-n!
end
count
The signatures in ports.rkt: (get-bytevector-n! p bytes start end), (get-string-n! p str start end)
(get-bytevector-n! p bytes start end)
(get-string-n! p str start end)
The signatures in R6RS: (get-bytevector-n! binary-input-port bytevector start count), (get-string-n! textual-input-port string start count)
(get-bytevector-n! binary-input-port bytevector start count)
(get-string-n! textual-input-port string start count)
You may find a test case for get-bytevector-n! in okuoku/yuni#95
The text was updated successfully, but these errors were encountered:
No branches or pull requests
get-bytevector-n!andget-string-n!both haveendinstead ofcountas argument, which is also reflected in that they do the wrong thing.The signatures in ports.rkt:
(get-bytevector-n! p bytes start end),(get-string-n! p str start end)The signatures in R6RS:
(get-bytevector-n! binary-input-port bytevector start count),(get-string-n! textual-input-port string start count)You may find a test case for
get-bytevector-n!in okuoku/yuni#95The text was updated successfully, but these errors were encountered: