[Libmesh-devel] PetscVector::operator=

2010-06-24 Thread Tim Kroeger
Dear all, In my application, I am doing quite a lot of assignments between NumericVector instances (which always are PetscVector instances in my case), and since I am lazily most of the time working in opt mode, I didn't realize that I was sometimes assigning vectors of different type, that is

Re: [Libmesh-devel] PetscVector::operator=

2010-06-24 Thread Jed Brown
On Thu, 24 Jun 2010 15:59:22 +0200 (CEST), Tim Kroeger wrote: > Dear all, > > In my application, I am doing quite a lot of assignments between > NumericVector instances (which always are PetscVector instances in my > case), and since I am lazily most of the time working in opt mode, I > didn'

Re: [Libmesh-devel] PetscVector::operator=

2010-06-24 Thread Roy Stogner
On Thu, 24 Jun 2010, Jed Brown wrote: > On Thu, 24 Jun 2010 15:59:22 +0200 (CEST), Tim Kroeger > wrote: > >> In my application, I am doing quite a lot of assignments between >> NumericVector instances (which always are PetscVector instances in my >> case), and since I am lazily most of the time

Re: [Libmesh-devel] PetscVector::operator=

2010-06-24 Thread Jed Brown
On Thu, 24 Jun 2010 12:16:53 -0500 (CDT), Roy Stogner wrote: > I suspect there are only two reasons why we didn't support mismatched > types: > > when that assertion was written we only had serial and parallel > vectors, a more extreme mismatch Yes, these are different in a deep way, they have