bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Integrate memoization into standard serialization. This involves a number of ↵	janakr	2018-03-13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	large changes: 1. SerializationContext and DeserializationContext become the owners of the Memoizer if requested. They produce new versions of themselves on demand that are memoization-aware. Because of intricacies of Skylark that I do not fully understand, we inject a Mutability object when starting memoization, and so to be conservative, that injection starts up a new memoization frame, nested if we were already memoizing, just like before. It would be nice to decouple this injection from memoization in the future. 2. MemoizingCodec is deleted, but really ObjectCodec becomes MemoizingCodec, so it lives on. BaseCodec is deleted since it now has only one implementation. 3. The simplified model of registering MemoizingCodecs is adopted for ObjectCodecs: all codecs are registered based on their #getEncodedClass and #additionalEncodedSubclasses. This also allows us to register codecs that are defined using tricky parameter types, since we're no longer trying to reflectively examine them. This required a clean-up of such codecs, and the addition of ArrayListCodec to stop NullableListCodec from making lists unmodifiable when they shouldn't be. 4. @AutoCodec is extended to allow users to specify that memoization should start with this codec. To ensure bit-equivalence, SkyKeySerializer disables memoization. PiperOrigin-RevId: 188918251
*	Tag Attribute, SkylarkDefinedAspect and some other Skylark classes with	mjhalupka	2018-03-12
\| \| \| \| \| \| \| \| \|	@AutoCodec. Remove Environment from SkylarkDefinedAspect. Add a note to BuiltInFunction that we shouldn't need to serialize it because all instances should be constant. PiperOrigin-RevId: 188763259
*	Rename Transition to ConfigurationTransition.	gregce	2018-01-30
\| \| \| \|	PiperOrigin-RevId: 183859414
*	Replace Attribute.Transition with config.transitions.Transition.	gregce	2017-12-22
\| \| \| \|	PiperOrigin-RevId: 179936355
*	Remove ConfigurationTransition.HOST references from lib.packages.	gregce	2017-12-20
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This removes the main barrier to making host transitions routine patch transitions. Today you signify a host transition by calling Attribute.Builder.cfg(ConfigurationTransition.HOST). Blaze's configuration machinery auto-converts this to HostTransition.INSTANCE, which is a patch transition. This change provides the groundwork for removing ConfigurationTransition.HOST and removing the special conversion logic. This also paves the way for better API support for multiple host configurations. Also change some cfg(HOST) rule references to cfg(HostTransition.INSTANCE). PiperOrigin-RevId: 179754619
*	Expose ObjcProtoAspect to Skylark.	cparsons	2017-12-20
	RELNOTES: None. PiperOrigin-RevId: 179737025