Bug 27963 - XS 5.8 Should Know C# 6 ?. operator
Summary: XS 5.8 Should Know C# 6 ?. operator
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 5.8
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2015-03-12 11:26 UTC by troy-dawson
Modified: 2015-03-13 07:34 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Screenshot of red squiggle (38.19 KB, image/png)
2015-03-12 11:26 UTC, troy-dawson

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description troy-dawson 2015-03-12 11:26:33 UTC
Created attachment 10297 [details]
Screenshot of red squiggle

Xamarin Studio
Version 5.8 (build 443)

This code:

new NSDictionary(path)?.ValueForKey(new NSString(key))?.ToString();

displays a red squiggle error (see attached screenshot) but compiles and runs correctly
Comment 1 Parmendra Kumar 2015-03-13 07:34:08 UTC
I have checked this issue and I am able to reproduce this issue using the latest stable build              Xamarin Studio : 5.8.443.  

This issue has been fixed in the upcoming build, and you will get Fix build soon. Here is the screencast for that fix:

Screencast: http://screencast.com/t/8NNmd3Lkyr

So as of now,  I am closing this issue.