-
Notifications
You must be signed in to change notification settings - Fork 188
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
IORef based socket #303
Merged
Merged
IORef based socket #303
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
b1a37e4
IORef for Socket.
kazu-yamamoto a20d24a
fix for Windows.
kazu-yamamoto 3de7d80
fix for Linux.
kazu-yamamoto 2a5c69a
moving close from Close to Types.
kazu-yamamoto 96d73e3
renaming Close to Shutdown.
kazu-yamamoto 7916e72
Safe closing and GCing Socket.
kazu-yamamoto 610dcb3
fix a typo.
kazu-yamamoto 7e6eea8
invalidating Socket in socketToHandle.
kazu-yamamoto 40801af
pre-calculating the show string of Socket.
kazu-yamamoto d536bdd
defining invalidSocket.
kazu-yamamoto a529f96
a proper error message for socketToHandle.
kazu-yamamoto d555e65
keeping CInt instead of String in Socket.
kazu-yamamoto File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
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.
I see you decided to go with
String
rather thanShortByteString
or similar. Perhaps slightly more expensive, but easily changed later, without compatibility issues. Are there any module dependency barriers here (circular dependencies or dependencies we want to avoid) to changing this later? Am I wrong about String being a "more expensive" representation to carry along with the socket?Of course this is unlikely to matter much...
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.
GHC 7.6 uses bytestring-0.10.0.2 which does not provide
ShortByteString
unfortunately.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.
Does it make more sense to carry around an ascii encoded
ByteString
andpack
it whenever it needs to be shown? UtilizingString
here means we are introducing a fair amount of indirection and bloat for aShow
instance.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.
That was my instinct also. (Though of course ByteString show is
unpack
, but that's just detail).Perhaps the approach should instead be to store the minimal information needed to avoid having to use
unsafePerformIO
later. To that end, just the lazy byte string form of the fd is enough.We could even store an
originalFd
as aWord32
value, whose different type should be enough to discourage misuse (bypassing the IORef).and then in the
show
instance use that:There's probably no need to pre-format the whole string (was my suggestion, sorry). We could keep in mind that Haskell is lazy, and so the (current) string would I think remain an unevaluated thunk until actually used. Not sure whether the thunk is cheaper to keep around than the string.
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.
I changed it to
data Socket = Socket (IORef CInt) CInt
.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.
That's fine. The field is not exported, and the module in which it is visible is small. So the immutable original
fd
is unlikely to get misused.