Type guided '&' translation

[ivojawer]

closes #663

Generates CAST for the & send node (check CCodeGenerator >> generateCASTInferredAnd: aTSendNode) depending on the type of the receiver and argument

• Throw an error when types mismatch
• Boolean -> translates to &&
• Anything else -> translates to &

A TType object was implemented to replace some types, yet most operations are still string-based 😢

[guillep]

What if the boolean is an argument?

methodWithAndIntegerReceiverAndBooleanArgument: arg [

	| receiver result |

	receiver := 1000.
	result := receiver & arg

and all variantas :)

• boolean & boolean
• boolean & int
• int & boolean
• int & int

[ivojawer]

The cases where both (arg and receiver) are boolean/int are covered with methodWithAndBooleanReceiver and methodWithAndIntegerReceiver. Maybe the name should reference the argument 😅

The other cases I considered them all the same test case (covered by this method), as they fall under the "if they are different types then throw an error" logic.

[guillep]

Yes, but my point is that those tests are on literal booleans/integers!!!
What if the receiver are the result of a more complex expression, say a variable? Do we need a type annotation for booleans?