Bug 38703 - Linq.Expression when assigned from a lambda exression aren't constructed correctly
Summary: Linq.Expression when assigned from a lambda exression aren't constructed corr...
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: 4.0.0
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2016-02-12 02:29 UTC by James Cook
Modified: 2016-02-15 16:03 UTC (History)
3 users (show)

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

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 GitHub or Developer Community 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 James Cook 2016-02-12 02:29:31 UTC
This unit test should pass:
using System;
using System.Linq.Expressions;
using NUnit.Framework;

namespace TestNamespace
    public class ExpressionTests
        class HasAction
            public void Start()

        public void TestExpressionHasCorrectObject()
            var expectedObject = typeof (HasAction).GetMethod("Start");

            Expression<Func<HasAction, Action>> methodToUse = r => r.Start;
            UnaryExpression unary = methodToUse.Body as UnaryExpression;
            MethodCallExpression methodCall = unary.Operand as MethodCallExpression;
            ConstantExpression constantExpression = methodCall.Object as ConstantExpression;

            Assert.AreSame(expectedObject, constantExpression.Value);

It currently fails under mono.
Comment 1 Marek Safar 2016-02-15 16:03:06 UTC
Fixed in master