thread-safety
Here are 77 public repositories matching this topic...
-
Updated
Nov 26, 2019 - Go
-
Updated
Sep 1, 2017 - Swift
It would be nice if someone can extend the readme file with proper conversion.
-
Updated
Mar 9, 2020
-
Updated
May 25, 2020 - C++
Unless I'm missing something, it seems the ACKQueue does not clean up after its self when you ACK the items. I discovered this function by looking over the unit tests. Is it expected that users call this function manually? It seems that clear_acked_data() should always be called after ackq.ack(item) if you don't want the sqlite DB to grow unbounded?
-
Updated
Sep 14, 2018 - C
-
Updated
Mar 11, 2020 - C++
-
Updated
May 1, 2019 - Swift
-
Updated
Oct 3, 2018 - Go
The comments of ghe cops show what kind of prectice is considered bad.
To improve it is alao relevant to understand what ia being considered the better practice.
Could you add examples or links to show how to do better in the comments?
-
Updated
Feb 5, 2020 - C
-
Updated
Feb 29, 2020 - Rust
-
Updated
Apr 19, 2018 - Go
-
Updated
Apr 20, 2018 - JavaScript
-
Updated
Jun 20, 2018 - Java
-
Updated
Jul 3, 2019 - Ruby
-
Updated
Nov 8, 2019 - C++
-
Updated
Feb 18, 2017 - Go
-
Updated
Apr 23, 2018 - Go
-
Updated
Mar 28, 2020 - Java
-
Updated
Aug 12, 2019 - Swift
-
Updated
May 24, 2020 - C
-
Updated
Oct 7, 2019 - Python
Improve this page
Add a description, image, and links to the thread-safety topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the thread-safety topic, visit your repo's landing page and select "manage topics."
const char* getIp(void) {
return "192.168.1.1";
}
above should be
const char* getIp(const el::LogMessage *l) {
return "192.168.1.1";
}