Fwd: [go-nuts] go/types#Check is not resolving external package source positions.

2017-10-29 Thread Keynan Pratt
-- Forwarded message -- From: Keynan Pratt Date: Sun, Oct 29, 2017 at 5:01 PM Subject: Re: [go-nuts] go/types#Check is not resolving external package source positions. To: roger peppe Thanks for the help Roger. On Sun, Oct 29, 2017 at 5:00 PM, Keynan Pratt wrote: >

Re: [go-nuts] The feature I want most, weak *

2017-02-13 Thread Keynan Pratt
eeds to quietly throw away the weak keyword when it is found in type declaration such that any code written to an experimental fork could be safely built with the official compiler. On Mon, Feb 13, 2017 at 5:04 PM, Ian Lance Taylor wrote: > On Fri, Feb 10, 2017 at 10:04 PM, Keynan

Re: [go-nuts] The feature I want most, weak *

2017-02-10 Thread Keynan Pratt
t added. I just think that's a shame. On Thu, Feb 9, 2017 at 11:04 PM, Keynan Pratt wrote: > In this scenario how does the runtime distinguish between a weak and strong > pointer? how does a developer ensure they are dealing with a weak or strong > pointer when declaring a struct? In