some setup
or external dependencies, must be run by passing the required build tags
explicitly.
Jose
El lunes, 7 de agosto de 2023 a las 9:38:40 UTC+2, TheDiveO escribió:
> https://stackoverflow.com/a/54734212
>
> On Monday, August 7, 2023 at 8:48:24 AM UTC+2 josvazg wrote:
>
>>
ual.
>
> On Fri, Aug 4, 2023 at 11:01 AM josvazg wrote:
> >
> > We are working on a project that requires some test helpers and mocks
> that, ideally, should:
> >
> > - Helpers should be accessible by all testing code, unit tests,
> integration or e2e.
&
We are working on a project that requires some test helpers and mocks that,
ideally, should:
- Helpers should be accessible by all testing code, unit tests, integration
or e2e.
- Note unit tests live along side normal code in their *_test.go
files.
- The rest of tests will be on a
> Put another way: if the code is OSS, but it depends on something that's
> not OSS and freely available, then can the code claim to be called OSS in
> the first place?
>
> On Saturday, 26 June 2021 at 08:34:13 UTC+1 josvazg wrote:
>
>> Maybe the answer is something like:
>
s for no good reason.
This is not as simple as just vendor on your same repo, but on the flip
side makes your exported repos more trustworthy and easier to consume.
Are there better ways to have the cake and eat it too?
WDYT?
Thanks,
Jose
El sábado, 26 de junio de 2021 a las 8:42:46 UTC
UTC+2, david@gmail.com
escribió:
> On Fri, Jun 25, 2021 at 1:23 PM josvazg wrote:
>
>> When working on internal company projects, it makes sense to use a
>> company wide GO Proxy assuring that all go dependency code is available and
>> immutable. But when you mov
When working on internal company projects, it makes sense to use a company
wide GO Proxy assuring that all go dependency code is available and
immutable. But when you move to an Open Source project, you cannot longer
use such private proxy.
I wonder what is the best practice recommendation for
Is there some idiomatic or well known way to deal with extra errors when
you are already recovering from or reporting an error condition?
The typical case is, you hit an error and need to release resources before
returning it. But the resources themselves may fail when closing them.
One
ISA variants to the compiler in the go codebase, before thinking
about plugins or alike.
Correct?
Jose
El domingo, 13 de septiembre de 2020 a las 21:14:10 UTC+2, Ian Lance Taylor
escribió:
> On Sun, Sep 13, 2020 at 1:50 AM josvazg wrote:
> >
> > This is not a proposal, just a
This is not a proposal, just a curiosity question to check if anyone in the
Go ecosystem has already thought on this issue and have some solutions in
mind.
I might be late to this realization, but nowadays is pretty clear Intel
monolithic ISA dominance is threatened. ARM is taking over Macs
Let me know if this or something similar was already proposed and rejected
for some reason but otherwise...
What if instead of trying to cram all into a single line we use a previous
line before the function or type definition explaining how the type
parameter aliases are to be interpreted.
Replying to myself. Here is a must read to understand the go runtime better and
its source code:
https://github.com/golang/go/blob/master/src/runtime/HACKING.md
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and
Also, any recommended entry point or guide to read the runtime source code?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Thanks a lot Ian!
My mind picture of the runtime is more detailed now. I guess for more I should
now read the code itself.
Just one side issue. You said:
"
Memory allocated on the stack in function F can not be used by callees
of F. After F returns, the memory is gone.
"
I don't quite get
.
7. GolangRT subset language not only is fuzzy and changing, it is also
very limited to me generally useful for anything else.
Thanks,
Jose
El martes, 24 de enero de 2017, 22:16:07 (UTC+1), Ian Lance Taylor escribió:
>
> On Tue, Jan 24, 2017 at 12:46 PM, josvazg <jos...@
Golang runtime has been fully translated to Go for a while now. I know I
could just read the source code directly but...
Is there any known or recommended documentation (talk, slides, article)
about the runtime Go code?
I am specially interested in anything that describes the Golang runtime
enero de 2017, 0:48:28 (UTC+1), Michael Jones escribió:
>
> Josvazg, Your notion of "globals safe" should allow init() functions as
> safe writers. They are always invoked serially.
>
> On Sun, Jan 1, 2017 at 7:29 AM <chrisst...@gmail.com > wrote:
>
>>
>>
I am trying to come up with a detailed definition of what a thread safe Go
program is (and is not). One that a (go) tool could check by analyzing the
code for me.
Here is what I got so far:
-
If there are no go statements, then the program is single threaded and
thus thread
uot;let me do this I know what I am doing" than run
into issues without noticing.
Thanks,
Jose
El martes, 13 de septiembre de 2016, 8:16:14 (UTC+2), Jan Mercl escribió:
>
> On Tue, Sep 13, 2016 at 7:53 AM josvazg <jos...@gmail.com >
> wrote:
>
> >
Thanks for all links and answers!
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit
Why does Go does not have a static race detector? What are the difficulties?
(just pointing me to the right docs to read is fine)
I was thinking in a naive high level way...
If Rust can do it, using its ownership model, Go could have a tool checking
the AST that analyzes variable scopes and
21 matches
Mail list logo
