Draft: add open_port & port_command support
#90
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes gleam-lang#89 port and process are still inextricably coupled, most of the complex things I would want to do already require process' recieve/subject tooling. the recursive dependencies are really a bitch too, I would much rather prefer `port` module define a lot of this stuff This integrates a lot of the port stuff into process.gleam since representing a port-based subject as PortSubject lets us do two things: - Disallow send() on PortSubjects with a panic - check subject_owner at runtime that the port subject is still the calling process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cast()for unsafely_create_subject callgleam/erlang/processFixes #89