mono 5.0 - xbuild deprecated, C# 7.0, concurrent garbage collector #464

Activity

1. vmuriart commented on May 12, 2017

   

   vmuriart

   on May 12, 2017

   Contributor

   More actions

   I've frozen the language to C# 6.0 when C# 7.0 features were rolling out. I don't want to upgrade the language (atleast not now).

   GC... I still have nightmares about our current GC setup, I don't think we want to further complicate it.

   The only actionable item I see here is the xbuild deprecation (i assume this will affect our Travis CI eventually) We'll have to play around w it to see how to set it up.
2. den-run-ai commented on May 13, 2017

   

   den-run-ai

   on May 13, 2017

   ContributorAuthor

   More actions

   I agree on C# 6.0 and xbuild, not sure about GC. Together with C#6.0 and xbuild, also underlying compiler is updated from "mcs" to "csc" (roslyn).
3. den-run-ai

   added

   easy

   on May 16, 2017
4. den-run-ai

   closed this as completedin #471on May 24, 2017
5. wesnerm commented on Jan 8, 2018

   

   wesnerm

   on Jan 8, 2018

   Last edited by wesnerm

   More actions

   Is it possible to add the C# 7.0 support back in, since competitive programming sites aren't using the csc build because it takes too much memory and the compiler is killed by the OS?
6. den-run-ai commented on Jan 8, 2018

   

   den-run-ai

   on Jan 8, 2018

   ContributorAuthor

   More actions

   can you give example of your problem, this does not make sense to me. so you need to use alternative to csc (mcs?) and support C# 7.0 in a code-base that calls into pythonnet?