Jump to content
oatkins

C# 7/Visual Studio 2017 support

Recommended Posts

Currently, new C# language features (e.g. tuple literals) cause parsing errors in SemanticMerge. Will the new language features be supported soon?

Share this post


Link to post
Share on other sites

Yes, it's in our roadmap supporting the new c# 7 release.

Unfortunately I can't give you an ETA, we are about to launch Plastic SCM 6 and it's really time consuming.

As soon as we start with it I'll upgrade this thread.

Share this post


Link to post
Share on other sites

I think this creates a larger concern that I'm wondering if you considered, namely that the C# team is planning a faster cadence with smaller 'dot versions' coming quaterly (See: https://medium.com/@jakubgarfield/c-7-0-and-beyond-with-mads-torgersen-36c44a047024, section 'The Future').  Will the Plastic team be able to keep up with the pace of these sorts of changes?  Obviously not all releases will require changes to semantic merge, but it definitely has to be a concern/consideration?

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×