Does this mean that the next time I update delve I need to delete the contents in the old folder, or maybe more adjustments?
发自我的小米手机在 depar...@redhat.com，2019年1月5日 上午7:46写道：Hey all,Just wanted to mention that I've moved Delve off of my personal GitHub account and onto the organization go-delve
Hey all,
Just wanted to mention that I've moved Delve off of my personal GitHub
account and onto the organization go-delve (just `delve` was already taken,
and the owner won't budge unfortunately...).
Other than the location of the repo nothing else has changed. The new
location is github.com/
Isn’t an easier and better source of resource utilization just to farm out each
program under consideration to “the crowd” and say, rewrite dnsd in Go.
For security verification purposes, you’d be going through each line of the
converted program anyway.
I still think it would be a nearly imposs
Ian Lance Taylor :
> To be honest, the second step, making the compiler (and linker)
> idiomatic Go, is still in progress.
I'm not even a bit surprised to hear that. :-)
--
http://www.catb.org/~esr/";>Eric S. Raymond
My work is funded by the Internet Civil Engineering Institute:
jake6...@gmail.com :
> On Thursday, January 3, 2019 at 5:46:39 PM UTC-5, Eric Raymond wrote:
> >
> > On Thursday, January 3, 2019 at 12:11:06 PM UTC-5, Jake Montgomery wrote:
> >>
> >> I would note that any tool that ports from C++, or even C, to Go is going
> >> to produce ugly, unmaintainable, a
On Fri, Jan 4, 2019 at 8:52 AM wrote:
>
> On Thursday, January 3, 2019 at 5:46:39 PM UTC-5, Eric Raymond wrote:
>>
>> On Thursday, January 3, 2019 at 12:11:06 PM UTC-5, Jake Montgomery wrote:
>>>
>>> I would note that any tool that ports from C++, or even C, to Go is going
>>> to produce ugly, un
On Fri, Jan 4, 2019 at 8:31 AM Kevin Conway wrote:
>
> There are several conditions that bypass recover. Another example is "fatal
> error: concurrent map read and map write". The error messages typically start
> with "fatal error" and represent a non recoverable exception in the run time
> rat
On Thursday, January 3, 2019 at 5:46:39 PM UTC-5, Eric Raymond wrote:
>
> On Thursday, January 3, 2019 at 12:11:06 PM UTC-5, Jake Montgomery wrote:
>>
>> I would note that any tool that ports from C++, or even C, to Go is going
>> to produce ugly, unmaintainable, and non-idiomatic code, at best.
>
There are several conditions that bypass recover. Another example is "fatal
error: concurrent map read and map write". The error messages typically
start with "fatal error" and represent a non recoverable exception in the
run time rather than a user defined condition.
I don't know the official ter
I tried to recover a stack overflow but I couldn't.
func main() {
defer func() {
src := recover()
fmt.Println(src)
}()
main()
}
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receivi
Thanks, that's a very helpful link!
On Thursday, January 3, 2019 at 9:36:10 AM UTC-5, Martin Möhrmann wrote:
>
> To keep backwards compatibility with go1 changing fmt to count in the 0x
> for the padding was discussed and abandoned in
> https://go-review.googlesource.com/c/go/+/22136/.
>
--
Yo
As was said above, the defer becomes active when executed, so defer func()
*before* the potential returns.
Also as was said just before that, the power is clear in more complex
situations. Imagine three things that must be set-up in advance and closed
down properly (open/close network link, files,
if err not equal nil ,defer not push stack yet,so it wont execute.
As below it will execute
func main() {
src, err := os.Open("text.txt")
defer src.Close()
if err != nil {
return
}
}
On Friday, January 4, 2019 at 2:09:51 PM UTC+8, 伊藤和也 wrote:
>
> In the first example, "ok" was n
Julia is a nightmare for peer reviewability.
Gonum exists largely because Matlab, NumPy and Julia did not satisfy.
On Fri, 2019-01-04 at 00:06 -0800, minfo...@arcor.de wrote:
> Am Mittwoch, 2. Januar 2019 22:51:07 UTC+1 schrieb kortschak:
> >
> >
> > Yeah, Gonum is 5 years old, and yet because
On Fri, Jan 4, 2019, 09:06 Am Mittwoch, 2. Januar 2019 22:51:07 UTC+1 schrieb kortschak:
>>
>> Yeah, Gonum is 5 years old, and yet because of the design of the
>> language handles some aspects of numerical and scientific coding far
>> better than Matlab/NumPy
>>
>>
> This is more than debatable. D
Am Mittwoch, 2. Januar 2019 22:51:07 UTC+1 schrieb kortschak:
>
> Yeah, Gonum is 5 years old, and yet because of the design of the
> language handles some aspects of numerical and scientific coding far
> better than Matlab/NumPy
>
>
This is more than debatable. Don't underestimate scientific comp
16 matches
Mail list logo
