Hi,
On Mon, Jul 02, 2018 at 12:04:14PM +0200, Julia Lawall wrote:
> use array.Array as A
> use matrix.Matrix as MM
>
> but then it doesn't recognize the type matrix.
>
> With the imports it doesn't recognize MM.set. What should be done
> instead?
the stdlib has changed location. In my case I
On Mon, 2 Jul 2018, Ralf Treinen wrote:
> Hi,
>
> On Mon, Jul 02, 2018 at 12:04:14PM +0200, Julia Lawall wrote:
>
> > use array.Array as A
> > use matrix.Matrix as MM
> >
> > but then it doesn't recognize the type matrix.
> >
> > With the imports it doesn't recognize MM.set. What should be
On Mon, 2 Jul 2018, Andrei Paskevich wrote:
> Hi Julia,
>
> you simply write "use array.Array" and "use matrix.Matrix" — the import will
> be done by default. You wirte "use ... as" when you _don't_ want import.
> And, of course, you still can write "use import array.Array as A" if you
> want
Hello,
I am trying to get my 0.88 code to work with why3 1.0. I have
use import array.Array as A
use import matrix.Matrix as MM
According to my understanding, the imports are no longer needed. I tried:
use array.Array as A
use matrix.Matrix as MM
but then it doesn't recognize the type
Hi Julia,
you simply write "use array.Array" and "use matrix.Matrix" — the import
will be done by default. You wirte "use ... as" when you _don't_ want
import. And, of course, you still can write "use import array.Array as A"
if you want to name the scope "A" _and_ to import it, too.
Best,
On Mon, 2 Jul 2018, Andrei Paskevich wrote:
> Hi Julia,
>
> you simply write "use array.Array" and "use matrix.Matrix" — the import will
> be done by default. You wirte "use ... as" when you _don't_ want import.
> And, of course, you still can write "use import array.Array as A" if you
> want
On Mon, 2 Jul 2018, Andrei Paskevich wrote:
> Hi Julia,
>
> you simply write "use array.Array" and "use matrix.Matrix" — the import will
> be done by default. You wirte "use ... as" when you _don't_ want import.
> And, of course, you still can write "use import array.Array as A" if you
> want
On 2 July 2018 at 14:56, Julia Lawall wrote:
> Previously, set was a function that returned the new matrix. Now the
> return type is unit. I think that this is the source of the problem.
Indeed, looking at stdlib/matrix.ml, there is no more pure applicative
version of "set" for matrices. This
On Mon, 2 Jul 2018, Andrei Paskevich wrote:
> On 2 July 2018 at 14:56, Julia Lawall wrote:
> > Previously, set was a function that returned the new matrix. Now the
> > return type is unit. I think that this is the source of the problem.
>
> Indeed, looking at stdlib/matrix.ml, there is no
