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

Set and get stream position #8

Open
tizoc opened this issue Oct 10, 2016 · 4 comments
Open

Set and get stream position #8

tizoc opened this issue Oct 10, 2016 · 4 comments

Comments

@tizoc
Copy link
Member

tizoc commented Oct 10, 2016

Stream position manipulation and query functions

There are no stream positions in Shen. Desired functionality:

  • go to the beginning of the stream
  • go to the end of the stream
  • go to an arbitrary position in the stream (relative to beginning, end or current position in stream)
  • query the current position in the stream

Current implementations

TODO: add others

@rkoeninger
Copy link
Member

@tizoc While we're clearing out the backlog, this and the other kernel-extension issues seem to be off-limits based on responses we've received before. I don't think they can be realized without changing kernel functionality (where the stuff under library/ is fine because it's in addition to the existing kernel)

@tizoc
Copy link
Member Author

tizoc commented Sep 8, 2019

At this point these are more about finding the common patterns across ports and provide a common API, either as a library (using cond-expand to decide what to do) or ports implementing a defined API. Not much to do for these for now other than wait.

@rkoeninger
Copy link
Member

Would ports offer such functionality under a common name? Usually, port- or platform-specific behavior has a port-prefix like shen-jvm.set-position or jvm.set-position.

@tizoc
Copy link
Member Author

tizoc commented Sep 9, 2019

Yes. Once a common api is figured, ports can provide a version of the library using their own primitives. Alternatively, a standard-library normalizes what ports already provide under a common api using cond-expand. At this point it doesn't matter much because most port don't provide these things, there is no rush to pre-define anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants