Don't mutate arrays in symmetric trig functions #1206
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Since these functions act on arbitrary
AbstractArrays, we should ideally not assume mutability of the intermediate arrayretmat. Instead, we may rely on the fact that theHermitianwrapper implicitly sets the imaginary components of the diagonal elements to zero. This change will mean that the parents do have non-zero imaginary components, but this may be seen as an implementation detail.Alternately, if this is not desired, we may explicitly set the diagonal elements for
StridedArrays, which are usually mutable.This PR will get the following to work, e.g.:
Prior to this, the method call errors, as an
SMatrixdoesn't supportsetindex!.Adding tests for this change is a little tricky, now that this repo is separated from julia, and the test helpers lie in the main julia repo. Any suggestions?