Assertion messages added
Refactor codegen of "in" expression

Use generateIn() twice, for binary expressions and for when clauses
Don't try to generate optimized "in" for LongRange

 #KT-4097 Fixed
Update year to 2014 in generated files
Add copyright and auto-generation notice to built-in sources
Change built-ins generators package from 'runtime' to 'builtins'
Refactor built-ins source generators
Add GenerateBuiltInsTest

Tests that generated sources of built-ins (Functions, Ranges, etc.) are
up-to-date
Remove outdated hack in DeclarationResolver
Fix variance in Progression and Range
Delete outdated hack in Unit
Revert "Using default renderer in LoadBuiltinsTest."

This reverts commit 1d21ebf882d9fa417f57f4468eb2dfe2032fb445.

Conflicts:
	compiler/testData/builtin-classes.txt
	core/descriptors/src/org/jetbrains/jet/renderer/DescriptorRendererImpl.java

Reverting a part of this (related to the field 'prettyFunctionTypes') because
will need to add a test that deserialized built-ins (obtained by
KotlinBuiltIns.getInstance()) are consistent with lazy resolved built-ins. This
test would break because while DescriptorRenderer renders pretty function types
it compares descriptors to the ones from KotlinBuiltIns, but in case of lazy
resolve descriptors created for built-ins would be different from
KotlinBuiltIns, so renderer wouldn't correctly render a function type
Check that lazy resolve works correctly on built-ins

This test is needed because BuiltInsSerializer uses lazy resolve to load and
serialize built-ins. We need to make sure that lazy resolve works exactly like
deserialization
Revert hack for annotations on built-ins

This reverts commit 5cae5c0338e9ace30c8d80f4a030981d9193c96e
Delete outdated j2k.ipr and Makefile from j2k
A small confusing typo

Here was an out-of-date error message. It could confuse developers about the function literal syntax.

"To specify it explicitly use the {(p : Type) => ...} notation"
Merge pull request #350 from voddan/patch-4

A small confusing typo
JS backend: made some asserts in AliasingContext and InnerDeclarationTranslator more informative.
JS backend: minor refactoring in LiteralFunctionTranslator
JS backend: refactoring LiteralFunctionTranslator -- make possible to store translation state and create an instance for each translation instead of one instance for all translations.
Introduced DefinitionPlace class and make creating a new definition place more safety.