Hang by your pseudopod, write if you find a warm rich planet ripe for conquest.
On 8 August 2017 at 22:49, Rob Pike wrote:
> Grep for conquest.
>
> -rob
>
>
> On Wed, Aug 9, 2017 at 6:58 AM, roger peppe wrote:
>> On 8 August 2017 at 21:34, Michael Jones
Grep for conquest.
-rob
On Wed, Aug 9, 2017 at 6:58 AM, roger peppe wrote:
> On 8 August 2017 at 21:34, Michael Jones wrote:
>> The Four Horsemen of the Apocalypse, surely! It would be tempting fate to
>> shade them or step on their brand.
>
> Ah,
On 8 August 2017 at 21:34, Michael Jones wrote:
> The Four Horsemen of the Apocalypse, surely! It would be tempting fate to
> shade them or step on their brand.
Ah, but of which apocalypse?
--
You received this message because you are subscribed to the Google Groups
The Four Horsemen of the Apocalypse, surely! It would be tempting fate to
shade them or step on their brand.
On Tue, Aug 8, 2017 at 5:54 AM, wrote:
> Thanks for suggesting the Reader(q0, q1 int64) io.RuneReader. I
> accidentally replied off list.
>
> I wasn't aware of up to
Thanks for suggesting the Reader(q0, q1 int64) io.RuneReader. I accidentally
replied off list.
I wasn't aware of up to four horsemen being involved. The man pages didn't
prepare me for this.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
On 8 August 2017 at 12:04, Rob Pike wrote:
> When I wrote that (1985?), I was misinformed about the Four Horsemen.
Which particular Four Horsemen would those be?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe
When I wrote that (1985?), I was misinformed about the Four Horsemen.
Also now "u-" is redo.
-rob
On Tue, Aug 8, 2017 at 8:59 PM, roger peppe wrote:
> It's nice to see this, but it would be nicer still if it
> was amenable to representations that weren't
> just a slice of
It's nice to see this, but it would be nicer still if it
was amenable to representations that weren't
just a slice of bytes (for example disk or network
backed files, or just something which made insertions
not O(n)). It seems like it might be possible
to use Regexp.FindReader* to avoid
I'm sure this has been done already, but I thought I'd share my
implementation of this here for anyone interested in using structural
regular expressions in Go. It doesn't cover 100% of what Edit does in Acme,
but its close enough that I can use the example program