Skip to content

Add godoc comments indicating that a mutex is needed for use with goroutines#22

Open
skidder wants to merge 1 commit into
rakyll:masterfrom
skidder:mention-thread-safety-in-godoc
Open

Add godoc comments indicating that a mutex is needed for use with goroutines#22
skidder wants to merge 1 commit into
rakyll:masterfrom
skidder:mention-thread-safety-in-godoc

Conversation

@skidder

@skidder skidder commented May 5, 2016

Copy link
Copy Markdown

No description provided.

@rakyll

rakyll commented Jun 30, 2016

Copy link
Copy Markdown
Owner

Could you rebase it? I cannot merge due to the conflict.

@skidder skidder force-pushed the mention-thread-safety-in-godoc branch from b8cc6e3 to 78a3d9b Compare July 12, 2016 23:25
@skidder

skidder commented Jul 12, 2016

Copy link
Copy Markdown
Author

@rakyll I've rebased my PR branch to incorporate more recent changes

Comment thread magicmime.go
// when it is no longer needed. Access to the magicmime
// database is not synchronized; the magicmime database file-descriptor
// is referenced through a global variable. Add mutex Lock/Unlock around
// the magicmime functions if using multiple goroutines.

@ctrochalakis ctrochalakis Jan 15, 2018

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that mean we should guard between calls to a specific Decoder's methods? Or between calls to magicmime.NewDecoder() calls? or both?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure that it's only between calls to a specific Decoder.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants