Skip to content
This repository has been archived by the owner on Mar 9, 2021. It is now read-only.

INTERNAL ERROR: ResolveResult ConversionResolveResult #435

Open
n9 opened this issue Jul 23, 2015 · 6 comments
Open

INTERNAL ERROR: ResolveResult ConversionResolveResult #435

n9 opened this issue Jul 23, 2015 · 6 comments
Labels

Comments

@n9
Copy link

n9 commented Jul 23, 2015

In develop, I am getting INTERNAL ERROR: ResolveResult [ConversionResolveResult System.Func1[[System.Threading.Tasks.Task1[[System.Int32]]]]] is an error. with this code:

            Func<Task<int>> f = async () =>
            {
                throw new Exception("Foo");
            };

Not sure whether it is already fixed on Roslyn/Bridge.Net 2.

@erik-kallen
Copy link
Contributor

Probably an NRefactory bug

@michaelcheers
Copy link

@n9, @erik-kallen, it is not an NRefactory bug as it works in Bridge.NET.

@n9
Copy link
Author

n9 commented Jun 12, 2017

@michaelcheers The current Bridge.NET is using the same NRefactory as Salterelle in 2015?

@geoffreymcgill
Copy link
Member

https://www.nuget.org/packages/Bridge.NRefactory
https://github.com/bridgedotnet/NRefactory

Includes several NRefactory bug fixes.

https://dev.deck.net/85d5a66bf8dc279df25567ed7473a44f

public class Program
{
    public static void Main()
    {
        Func<Task<int>> f = async () =>
        {
            throw new Exception("Foo");
        };
    }
}

@n9
Copy link
Author

n9 commented Jun 13, 2017

@michaelcheers

If something works in current Bridge.NET and not in Saltarelle, it does not mean that it could not be caused by an NRefactory bug. Saltarelle was acquired by Object.NET, however Object.NET let it die. It is no longer developed, dependencies are not updated. (For more information, please read #430.)

I am not sure why are you commenting old bugs in Saltarelle. If the reason is that you are searching for alternative to Bridge.NET, I would suggest you to learn F# and try http://fable.io/.

In case you are going to migrate a larger code base from Saltarelle to Bridge.NET. I would suggest you to wait until all portarelle issues are resolved. Otherwise, you might get crazy after several days of migration that thinks works differently in Bridge.NET. (I do not know ETA of all portarelle issues to be cleared.)

@geoffreymcgill
Copy link
Member

geoffreymcgill commented Jun 13, 2017

Hi @n9 – The outstanding 40 portarelle issues haven't been reviewed in a while, but we were just talking about this task in our team meeting. We'll try out best to review and update the issues again soon. With a quick scan, there are certainly several portarelle issues that are now supported and can be closed.

Most of the items on that list, and any other Saltarelle features missing from Bridge, will only be dealt with if the community requests.

Be sure to review the Upgrade from Saltarelle wiki document if you're moving from Saltarelle to Bridge.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants