# Talk:Display a linear combination

## Wat?

There's a variety of ways of implementing linear combinations, and this particular task is requiring a representation which will not be executable in many languages. So it would be good to add some motivation to the task description. Why would someone want to do this? --Rdm (talk) 16:15, 13 October 2015 (UTC)

- I was working on my Perl 6 Geometric Algebra library and I needed some way of displaying a multivector. By default I had an output like this one:

MultiVector.new(blades => (my Real %{UInt} = 0 => 1, 4 => 1, 10 => 3))

- Which is the output from , and it is clearly not satisfying. I wanted an output that looks like the input. The more I thought about it the more I was annoyed by the idea that in order to have something that looks good I would have to make sure I don't display the scalars if they are 1, and that I use a subtraction where appropriate. It was looking like quite a hassle,so I thought: « why not make a rosetta task so that I can steal the solution from others? » :-)

- As a matter of fact soon after I created the task I realized I could get a simple solution by using string substitutions on the output, so I was actually able to write the first solution in Perl 6.

- I still think it's a useful task, as it can be used for instance to display complex numbers or quaternions. In perl 6 for instance the output for complex numbers is not perfect. i is displayed as '0+1i;', which to me is acceptable but not so great. With Math::Quaternions it's much worse and arguably not acceptable.

- I'm not sure what you mean when you say that the syntactic constraints are tailored towards perl6. An expression like is not language specific. It's how you write a linear combination in standard math. Let me remind you that this task is about
*output*, not*input*. If I'm not mistaken your predilection language, J, as an elaborate syntax and I'm sure there are plenty of ways to create a linear combination, but a human friendly, and mathematically conventional way of displaying such linear combination is quite universal. In fact in Perl 6 we could use any syntax we want since we could create a slang or something. I've just picked one that corresponds to the way we write algebraic expressions in maths, regardless of the programming language.--Grondilu (talk) 23:54, 13 October 2015 (UTC)

- I'm not sure what you mean when you say that the syntactic constraints are tailored towards perl6. An expression like is not language specific. It's how you write a linear combination in standard math. Let me remind you that this task is about

- Ok, so that's what it is. In that case, the spec should still be documented in the task description - it's just not perl6 like I thought it was. Of course, you are hindered by the fact that "Standard Math" isn't very standard - it was created just a few years ago, and is a rather slippery collection of concepts also. I tried finding a definitive definition, and the best I found was an inexact common core document with a 2015 copyright on it. So most older math texts won't be using it, for example and it's difficult to talk about. (I expect the part of the definition you are using has been around a few years, but not a few decades. And I expect there's some corner of standard math which states that a linear combination like you are describing here could be expressed as (-1,-2,0,-3)*e or something not too far from that - with the summation being implicit.)

## Formulae left invisible to most browsers by edit of 21:43, 10 July 2016

Cosmetic edits made to the task page at 21:43, 10 July 2016, including the injection of spaces around expressions in <math> tags, have left most formulae in the task description completely invisible to all browsers which display the graphic file version of formulae rather than processing the MathML (this is, in fact, the majority of browsers). The MediaWiki processor does not currently expect such spaces, and generates syntactically ill-formed HTML if they are introduced. Other aspects of these cosmetic edits may further compound the problem. Hout (talk) 18:48, 21 September 2016 (UTC)