On Sat, 2023-07-01 at 22:34 -0700, Mike Schinkel wrote:
> > What is the difference to if err != nil { goto } ?
>
> Thanks you for asking.
>
> If you run go fmt on a file that contains the formatting you ask
> about the line will be expanded to the 3 lines, which brings us back
> to status quo:
Hi Sven,
> *What is the difference to if err != nil { goto } ?*
Thanks you for asking.
If you run *go fmt* on a file that contains the formatting you ask about
the line will be expanded to the 3 lines, which brings us back to status
quo:
*if *
*err != nil { goto } *Of course *go fmt*
The undefined reference errors means that you gave it headers for rocksdb
but you forgot to give it the corresponding library flag that starts with
-l like -lyour_rocksdb_library_name (I don't know what the rocksdb or go
shim to rocksdb library you are using is called; you'll have to figure
Any update on this? I wanted to use the register-based calling convention
as well and got "ABI selector only permitted when compiling runtime", too.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop
Mike Schinkel schrieb am Fr. 30. Juni 2023 um 07:04:
*when err!=nil goto *
What is the difference to `if err != nil { goto }` ?
Go is awesome, because it does _not_ more and more syntax, especially with
subtle nuances that one has to remember.
>
--
You received this message because you
