Open Radar

 
Summary:
Each IntegerType-conforming type implements a set of endian-handling features: big-endian and little-endian initializers and properties, plus a byteSwapped property. These should be declared in a protocol they all conform to.

Steps to Reproduce:
1. Declare a generic function that takes IntegerTypes:

    func readIntegerFromPacket<Integer: IntegerType> (packet: [UInt8]) -> Integer {
        let integerSizedThing: Integer = readRawIntegerFromPacket(packet)

2. Try to use one of the endianness features:

        return integerSizedThing.bigEndian
    }

Expected Results:
You can.

Actual Results:
You can’t. This behavior is not part of any protocol, even though all integer types have identically-named and identically-functioning members for this function.

Notes:
This could be part of the IntegerType protocol, but it might actually make sense to put it in a separate protocol that both IntegerType and FloatingPointType conform to, and to add endian-handling functionality to the floating-point types.