Another choice to throw into the mix is
https://github.com/cockroachdb/copyist. It comes with different trade offs
but if you buy into its framework, it should be much faster than running
the database.
On Thu, Jul 29, 2021 at 3:13 AM Brian Candler wrote:
> You might also want to look at podman,
A situation has arisen a few times lately where we've seen segfaults that
have strange looking address values. Another thing that makes the situation
confusing is that the memory referenced by the stack trace should have been
allocated at init time. This seems to only be happening on macOS. The
; On 22. Feb, 2021, at 16:02, Andrew Werner wrote:
> >
> > Hi Paul,
> >
> > What makes you say that that is “heavyweight”? For what it’s worth, many
> of those modules used to just be directories inside the pgx library.
> Splitting them out has been good for the
Hi Paul,
What makes you say that that is “heavyweight”? For what it’s worth, many of
those modules used to just be directories inside the pgx library. Splitting
them out has been good for the ecosystem. In general, I’d encourage you not
to worry about a small handful of transitive dependencies,
Hey Roger,
Thanks for taking the time to engage with me on this. Really appreciate it!
On Monday, June 22, 2020 at 6:01:46 PM UTC-4, rog wrote:
>
>
>
> On Mon, 22 Jun 2020 at 22:49, Andrew Werner > wrote:
>
>>
>>
>> On Monday, June 22, 2020 at 5:42:12 PM
On Monday, June 22, 2020 at 5:42:12 PM UTC-4, rog wrote:
>
>
> Thanks for pointing this out. I'm cool with this approach. I'll update my
>>> library to utilize it (and consider also adopting the list.List, though I
>>> do like my freedom to pool list nodes).
>>>
>>
> Personally, I'd start by
On Monday, June 22, 2020 at 10:17:01 AM UTC-4, rog wrote:
>
>
>
> On Mon, 22 Jun 2020 at 14:59, Andrew Werner > wrote:
>
>>
>>
>> On Mon, Jun 22, 2020 at 9:45 AM roger peppe > > wrote:
>>
>>>
>>>
>>> On Mon, 22 Jun 202
On Mon, Jun 22, 2020 at 9:45 AM roger peppe wrote:
>
>
> On Mon, 22 Jun 2020 at 14:26, Andrew Werner wrote:
>
>> Hey Rog,
>>
>> I think I sent you a private reply earlier. My bad. I now see what you're
>> proposing in the first proposal think it makes a
global variables). I suspect that might turn out to be an
> anti-pattern. Instead, using function or interface value that operates on
> the pointer is strictly more general, I think, and doesn't suffer from that
> problem.
>
> cheers,
> rog.
>
>
> On Sun, 21
In order to get a zero value, does the following work today? Is it
acceptable?
func GenericFunc(type T)() T {
return func() (t T) { return t }()
}
This could also just be written like below but above I was trying to
demonstrate how to make a zero value within another function.
func
ype [...]T
}
Thanks for dealing with my very long-winded way of saying that.
On Sunday, June 21, 2020 at 12:35:53 PM UTC-4, David Finkel wrote:
>
>
>
> On Sat, Jun 20, 2020 at 1:22 AM Andrew Werner > wrote:
>
>> [The body of this email is a duplication of the README
[The body of this email is a duplication of the README in
https://github.com/ajwerner/go2dequeue/
which also contains the sample implementation]
Exercise building a dequeue with the go2 Type Parameter Draft
This project is an exploration with the go2go / Type Parameters - Design
Draft
12 matches
Mail list logo
