I usually just use patch commits:
git add -p
On Tuesday, April 27, 2021 at 10:24:51 AM UTC-4 Reto wrote:
> On Mon, Apr 26, 2021 at 11:59:47PM -0700, christoph...@gmail.com wrote:
> > Thank you for pointing this out. I wasn’t aware of it. But the question
> > still holds for published main progra
Hello,
https://github.com/icholy/gomajor
This is a tool that tries to alleviate some of the toil that comes with
SIV. I've been working on it on and off for a while and am looking for
testers/feedback.
Thanks,
- icholy
--
You received this message because you are subscribed to the Google Gro
Your code doesn't even compile.
On Thursday, October 31, 2019 at 1:13:50 PM UTC-4, kevma...@gmail.com wrote:
>
> I apologize for submitting yet another go format "issue". I'm more so
> gauging the community on this idea. Furthermore, I ask that you understand
> I'm not sure if this type of code
gt; Jochen
>
> On Wednesday, 18 September 2019 14:37:49 UTC+1, Ilia Choly wrote:
>>
>> You should try to make Conn implement io.Reader and io.Writer
>>
>> On Tuesday, September 17, 2019 at 6:29:08 PM UTC-4, Jochen Voss wrote:
>>>
>>> Dear all,
>>&g
You should try to make Conn implement io.Reader and io.Writer
On Tuesday, September 17, 2019 at 6:29:08 PM UTC-4, Jochen Voss wrote:
>
> Dear all,
>
> Because I wanted to learn about the websocket protocol, I have implemented
> a websocket server in Go:
>
> code: https://github.com/seehuhn/go
he
> fiction that the accepted type is `*T`). I'm not sure what the best way of
> write such a constraint is, though, or how common this kind of case is.
>
> On Mon, Jul 29, 2019 at 2:25 PM, Ian Lance Taylor > wrote:
>
>> On Mon, Jul 29, 2019 at 7:05 AM Ilia Choly >
When converting a non-pointer value to an interface, pointer methods cannot
be used to satisfy the interface. Even though the compiler could add
instructions to take the value's address, this is not allowed because it's
error prone. Since pointer methods usually mutate the receiver, you don't
w
