Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining a function in one cell and calling it in another results in compilation error #38

Closed
4 of 13 tasks
eerhardt opened this issue Jul 25, 2019 · 3 comments · Fixed by dotnet/roslyn#38550
Closed
4 of 13 tasks
Assignees

Comments

@eerhardt
Copy link
Member

Describe the bug

See the screen shot below.

I created a notebook, imported an assembly, defined a function that took a parameter of a type from that assembly in a cell. When I tried invoking the function in another cell I got a compilation error:

(2,6): error CS1503: Argument 1: cannot convert from 'Microsoft.ML.IDataView [/Users/eerhardt/.nuget/packages/microsoft.ml.dataview/1.2.0/lib/netstandard2.0/Microsoft.ML.DataView.dll]' to 'Microsoft.ML.IDataView [Microsoft.ML.DataView, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51]'

Did this error occur while using dotnet try or online?

  • dotnet-try
  • online

What kind of error was it?

  • User Interface (UI): For example the output never displayed
  • Service Error: For example "The service is temporarily unavailable. We are working on it"
  • Other:

Screenshots

If applicable, add screenshots to help explain your problem.
Screen Shot 2019-07-25 at 2 10 52 PM

Please complete the following:

  • OS
    • Windows 10
    • macOS
    • Linux (Please specify distro)
    • iOS
    • Android
  • Browser
    • Chrome
    • Edge
    • Safari
@pgovind
Copy link
Contributor

pgovind commented Aug 15, 2019

I just ran into this too. Here's what I was trying to do:

Bug

df is defined in the cells above(not included in the screenshot).

@svick
Copy link

svick commented Aug 15, 2019

I suspect this is the same issue as dotnet/roslyn#23123.

@eerhardt
Copy link
Member Author

I believe we are going to need a fix for this issue before the notebook experience is a viable option for customers. Without this being fixed I can't imagine getting any real work done in a C# notebook.

@tmat tmat closed this as completed Sep 17, 2019
@jonsequitur jonsequitur transferred this issue from dotnet/try Jan 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants