Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Terminate is the only way to exit?
See original GitHub issueIt does not appear the it would be possible to signal the event loop to exit gracefully. The note on terminate says that it exits without dropping. Does that mean the WebView is leaked? Is there a better method for exiting from inside the invoke_handler?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Terminating threads
A process can exit at any time when a thread calls the exit subroutine. Similarly, a thread can exit at any time by...
Read more >Exit statement (VBA)
Provides a way to exit a For loop. It can be used only in a For...Next or For Each...Next loop. Exit For transfers...
Read more >Exit a loop in C++
Some common ways to exit a loop are as follows: Break: This statement is a loop control statement used to terminate the loop....
Read more >Terminating a Java Program
System.exit() is a method that causes JVM to exit. ... So return; does not really terminate your java program, it only terminates your...
Read more >Different ways to terminate a program in C
Starting with the most widely used and most obvious function that is by using the exit() function. Some of the common ways to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, the deprecation notice is definitely wanted, no need to create unnecessary breakage. I will probably release 0.6 after your PR gets merged, keep the deprecation during 0.6 and remove the method in 0.7.
I totally agree with @zxey, but would caution against just removing an interface that has been there for a long time, no matter how confusing or semantically dualistic. A breaking change is a breaking change. That’s why I really appreciate @FreeMasen 's thought to at least consider downstream consumers with the deprecation notice.