<commit_before>Latest
----------

* ";" can no longer be used to demarkate an empty case in a switch statement,
  use "break" instead.


2014-05-07
----------

* The compiler's ability to diagnose many common kinds of type check errors has
  improved. ("expression does not type-check" has been retired.)

* Ranges can be formed with floating point numbers, e.g. "0.0 .. 100.0".

* Convenience initializers are now spelled as "convenience init" instead of with
  the "-> Self" syntax.  For example:
  
    class Foo {
      init(x : Int) {}  // designated initializer
      
      convenience init() { self.init(42) } // convenience initializer
    }

  Initializers in extensions are still implicitly convenience initializers.  

* Reference types using the CoreFoundation runtime are now imported as
  class types.  This means that Swift will automatically manage the
  lifetime of a CFStringRef the same way that it manages the lifetime
  of an NSString.

  In many common cases, this will just work.  Unfortunately, values
  are returned from CF-style APIs in a wide variety of ways, and
  unlike Objective C methods, there simply isn't enough consistency
  for Swift to be able to safely apply the documented conventions
  universally.  The framework teams have already audited many of the
  most important CF-style APIs, and those APIs should be imported<commit_msg>clarify this comment.<commit_after>Latest
----------

* ";" can no longer be used to demarkate an empty case in a switch statement,
  use "break" instead.


2014-05-07
----------

* The compiler's ability to diagnose many common kinds of type check errors has
  improved. ("expression does not type-check" has been retired.)

* Ranges can be formed with floating point numbers, e.g. "0.0 .. 100.0".

* Convenience initializers are now spelled as "convenience init" instead of with
  the "-> Self" syntax.  For example:
  
    class Foo {
      init(x : Int) {}  // designated initializer
      
      convenience init() { self.init(42) } // convenience initializer
    }

  You still cannot declare designated initializers in extensions, only
  convenience initializers are allowed.

* Reference types using the CoreFoundation runtime are now imported as
  class types.  This means that Swift will automatically manage the
  lifetime of a CFStringRef the same way that it manages the lifetime
  of an NSString.

  In many common cases, this will just work.  Unfortunately, values
  are returned from CF-style APIs in a wide variety of ways, and
  unlike Objective C methods, there simply isn't enough consistency
  for Swift to be able to safely apply the documented conventions
  universally.  The framework teams have already audited many of the
  most important CF-style APIs, and those APIs should be imported
{'fraction_non_alphanumeric': 0.06822262118491922, 'fraction_numerical': 0.011490125673249552, 'mean_word_length': 3.3060278207109737, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7536266', 'n_tokens_mistral': 747, 'n_tokens_neox': 707, 'n_words': 373}