Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
byte *x = null;
When I type the ";"
It inserts a space between the "*" and "x".
This should not happen
Was an issue in the formatting engine not visiting the composed types. I really need to rework the formatting code :/.
It now formats correctly as "byte* x;"
Please, use C notation, not the C++ one:
We can make an option for it - I've never seen anyone doing the C notation in C#.
"byte *x" is very obscure in C#. See this example which type has y:
byte *x, y;
And what about "byte? x" are you typing "byte ?x"?
As said I can add an option for pointers. Should that be in the 'mono' style ?
btw. we should change the default formatting to something other than mono - I still think allman/vs.net is the way to go.
Very good observation.
I understand the scenario for "byte *x, y"
How if I only have "byte *x", the IDE does not reformat my code?
hm, that's easy:
Go to options -> text editor -> Behavior
And turn off on the fly code formatting.
But the goal should be to create t he best on the fly formatting engine possible, unfortunately that requires 100.000 +-5 options.