On Wednesday, 27 January 2021 at 23:28:17 UTC+1 Ian Lance Taylor wrote:
To be clear, there is no Go 2, and there are no plans for Go 2.
Speaking as one who suffered through the ill-conceived and interminable
Python3 transition, this is the best news I've heard since discovering and
falling in
On Thu, Jan 28, 2021 at 3:43 AM 'Carla Pfaff' via golang-nuts
wrote:
>
> On Wednesday, 27 January 2021 at 23:28:17 UTC+1 Ian Lance Taylor wrote:
>>
>> To be clear, there is no Go 2, and there are no plans for Go 2.
>
>
> For someone who follows the mailing lists and issue comments this has been
On Wednesday, 27 January 2021 at 23:28:17 UTC+1 Ian Lance Taylor wrote:
> To be clear, there is no Go 2, and there are no plans for Go 2.
>
For someone who follows the mailing lists and issue comments this has been
known for a while, but it's easy to see where the confusion comes from,
given
On Wed, Jan 27, 2021 at 1:10 PM clément auger wrote:
>
> I am wondering if some backward compatibility is planned for programs heavily
> relying
> on ast, parser, type, packages packages to analyze, interpret, manipulate go
> source code.
>
> I read this morning the blog and it says
> 'The
Programs written against a current Go version should continue to work
indefinitely.
So, yes, if you don't want to take advantage of generics (or other Go 2
changes), you don't have to do any work to have your program continue to
work. That's why I don't like the "Go 2" label - there just won't be
Hello,
I am wondering if some backward compatibility is planned for programs
heavily relying
on *ast, parser, type, packages* packages to analyze, interpret, manipulate
go source code.
I read this morning the blog and it says
'The language changes are fully backward compatible' in its last
