[go-nuts] I'd like to write a CSS StyleSheet Parser but...

2021-01-02 Thread atd...@gmail.com
Hello, I am currently in need of a css stylesheet parser to retrieve the CSSOM as a go datastructure. (probably in a map[*selector* string]map[*cssproperty* string]interface{}) The existing Go libraries that can be found online are a bit lacking in that respect, imho. But I also have never wri

Re: [go-nuts] Generics and formatting

2021-01-02 Thread Ian Lance Taylor
On Sat, Jan 2, 2021 at 10:28 AM 'Brian Candler' via golang-nuts wrote: > > Raised as https://github.com/golang/go/issues/43470 Thanks. Ian > On Friday, 1 January 2021 at 18:40:36 UTC Ian Lance Taylor wrote: >> >> On Fri, Jan 1, 2021 at 9:50 AM 'Brian Candler' via golang-nuts >> wrote: >> > >

Re: [go-nuts] Generics and formatting

2021-01-02 Thread 'Brian Candler' via golang-nuts
Raised as https://github.com/golang/go/issues/43470 On Friday, 1 January 2021 at 18:40:36 UTC Ian Lance Taylor wrote: > On Fri, Jan 1, 2021 at 9:50 AM 'Brian Candler' via golang-nuts > wrote: > > > > Just a minor issue, but playing with this example: > > https://go2goplay.golang.org/p/IUL1QDrtOw

Re: [go-nuts] Re: goproxy.io was deployed in independent region in Europe and America

2021-01-02 Thread Jan Mercl
On Sat, Jan 2, 2021 at 4:29 AM not...@gmail.com wrote: > > @Amnon, I'm sorry I have no idea why the graphs are missing, Seems your mailer does not embed images the way many mail clients understand it. In Gmail I get plain text instead ``, so there míght be some extra quoting happening somewhere.

Re: [go-nuts] Generics Error - How to fix?

2021-01-02 Thread da...@suarezhouse.net
Thank you!  My personal opinion from this small journey into this topic is what you all built here is very flexible and robust.  Are you all at the point of "perfect is the enemy of the good"?  What is the criteria that will define when this releases? As I see it, if

Re: [go-nuts] Re: Generics - please provide real life problems

2021-01-02 Thread Kevin Chadwick
>> Fair enough. > >It could be a first step (genrics only in the stdlib) before opening >generics to everybody. This stdlib trial approach might allow a spec to mature without the compatibility promise? Is there a danger that it evolves to favour implementers over readers? Should support for