Hello,
I'm working on a project where there is a very (machine generated) large
slice literal in the source tree: around 6MB. The slice is declared in a
separate file, and it contains instances of an interface.
Each time I use go-guru (go-guru-referrers, for example) in emacs, it takes
a
than go-guru in
this matter.
/David
Den fredag 7 december 2018 kl. 17:53:03 UTC+1 skrev David Wahlstedt:
>
> Hi,
> I am still quite inexperienced in go programming, and I find it quite
> frustrating, sometimes, to find what will actually be executed by a call to
> an interfa
Hi,
I am still quite inexperienced in go programming, and I find it quite
frustrating, sometimes, to find what will actually be executed by a call to
an interface method found in some arbitrary code.
Here I have traced the process of finding the definition of "conn.Close()"
an instance of an
skrev Sebastien Binet:
>
>
>
> On Wed, Sep 26, 2018 at 2:29 PM David Wahlstedt > wrote:
>
>> Thanks--nice!
>> Will this be less reliable than the built-in Ticker (that uses
>> runtimeTimer), besides the intentional randomness?
>>
>
> modulo the possi
onsdag 26 september 2018 kl. 17:33:29 UTC+2 skrev Sebastien Binet:
>
>
>
> On Wed, Sep 26, 2018 at 2:29 PM David Wahlstedt > wrote:
>
>> Thanks--nice!
>> Will this be less reliable than the built-in Ticker (that uses
>> runtimeTimer), besides the intentional ra
Thanks--nice!
Will this be less reliable than the built-in Ticker (that uses
runtimeTimer), besides the intentional randomness?
/David
Den tisdag 25 september 2018 kl. 18:43:33 UTC+2 skrev Sebastien Binet:
>
>
>
> On Tue, Sep 25, 2018 at 11:34 AM David Wahlstedt > wrote:
>
&g
to trigger the ticker.
>
> It wouldn't have to be that intensive a search, you could for example run
> the search itself on a regular ticker like every 100ms to drop the
> processing load, but within a fairly wide margin it will be quite random.
>
> On Tuesday, 25 September 2018 11:34:14
Hi,
What would be a nice way to implement a ticker that generates events
according to a Poisson process?
The built-in Ticker in ticker.go uses a runtimeTimer that has a field
called period.
I would like to implement a "random ticker" such that each tick interval is
random, using ExpFloat64() *
:
>
> On Fri, Mar 9, 2018 at 12:27 AM, David Wahlstedt
> <david.wah...@gmail.com > wrote:
> >
> > But it would still be nice to have GLR in goyacc, for instance in order
> to
> > write an ASN.1 parser.
>
> I'm not aware of anybody working on that.
Ok, I see!
But it would still be nice to have GLR in goyacc, for instance in order to
write an ASN.1 parser.
Den torsdag 8 mars 2018 kl. 20:06:44 UTC+1 skrev Jan Mercl:
>
> On Thu, Mar 8, 2018 at 7:44 PM David Wahlstedt <david.wah...@gmail.com
> > wrote:
>
> >
Hi,
I wonder if there are any plans to add the "glr" option to goyacc (it
doesn't look as if this is the case) ?
According to this thread,
https://stackoverflow.com/questions/25976394/how-to-resolve-ambiguity-in-the-definition-of-an-lr1-grammar
golang is "not LALR(1), nor LR(k) for any k".
So,
Correction of my comment: "looked deep into this" -> "not looked deeply
into this" ;-)
Den måndag 19 februari 2018 kl. 15:15:01 UTC+1 skrev David Wahlstedt:
>
> There is also the following repo, that uses parser generators a la
> yacc/lex to parse ASN.1 specific
alis%2Fasn1=D=1=AFQjCNFmZoHHNRpUYzvbvbdxCDwxFnlAbA>
> might
> be interested in supporting it / accepting a pull request to add it.
>
> On Fri, Jan 12, 2018 at 9:50 AM David Wahlstedt <david.wah...@gmail.com
> > wrote:
>
>> ASN.1 is still alive and present in telec
;
> On Fri, Jan 12, 2018 at 9:50 AM David Wahlstedt <david.wah...@gmail.com
> > wrote:
>
>> ASN.1 is still alive and present in telecom applications. The PER
>> encoding is missing in the go library, unfortunately...
>>
>>
>> Den torsdag 11 januari 20
ASN.1 is still alive and present in telecom applications. The PER encoding
is missing in the go library, unfortunately...
Den torsdag 11 januari 2018 kl. 20:04:50 UTC+1 skrev Pat Farrell:
>
> On Thursday, January 11, 2018 at 10:50:24 AM UTC-5, David Wahlstedt wrote:
>>
Hello,
I wonder if there are any plans to add PER encoding/decoding support for
ASN.1?
I have looked around, and it seems that there isn't any project supporting
this, currently.
Best regards
David
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
16 matches
Mail list logo