Integers in Swift were down casted to 32 bits integers. Fixed #688
Test case for ignoredProperties on Swift. Issue #686.
Merge pull request #706 from Reflejo/fix-swift-long-property-testcase

Test case for ignoredProperties on Swift. Issue #686.
Merge pull request #707 from realm/rogernolan-master

Minor fix to RLMArray -description.
improved tests for RLMArray -description
A couple negative keying tests
Similar setObject tests
Boxed 0.
Add Swift versions of some RLMArray tests
Merge pull request #710 from realm/os-RLMObject-UnknownKey

A couple negative objectForKeyedSubscript tests
fix for standalone RLMArray creation with array literals
Merge pull request #714 from realm/tg-swift-array-tests

Add Swift versions of some RLMArray tests
changelog
Merge pull request #715 from realm/al-standalone-literal

Fix for standalone RLMArray creation with array literals
Added preprocessor conditional for choosing property type according to running arch
Merge pull request #695 from Reflejo/swift-long-property-fix-2

Integers in Swift were down casted to 32 bits integers. Fixed #688
Move the default realm path on OS X to Application Support

And when not running in a sandbox, use the bundle identifier as a
subdirectory name so that each application has its own default realm
file rather than sharing them, falling back to the executable name if
it's not running in a bundle.
Create the directory containing the realm file if it does not exist
Mark -[RLMArray init] and +[RLMArray new] as unavailable

This makes trying to call either of these messages a compilation error.
Add documentation for RLMArray init and new