aboutsummaryrefslogtreecommitdiff
path: root/website/features/experimental/index.html
blob: 1128787c6d3b60f1921b07a6a993f10df3530f0a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
<!DOCTYPE html>
<html><head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<link rel="stylesheet" type="text/css" href="../../logi/reset.css" />
	<link rel="stylesheet" type="text/css" href="../features.css" />
	<link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" />
	<meta name="description" content="Spice up your java" />
	<title>Lombok feature overview</title>
</head><body><div id="pepper">
	<div class="minimumHeight"></div>
	<div class="meat">
		<div class="header"><a href="../../index.html">Project Lombok</a></div>
		<h1>Lombok experimental features</h1>
		<div class="index overview">
			Experimental features are available in your normal lombok installation, but are not as robustly supported as lombok's main features.
			In particular, experimental features:<ul>
				<li>Are not tested as well as the core features.</li>
				<li>Do not get bugs fixed as quickly as core features.</li>
				<li>May have APIs that will change, possibly drastically if we find a different, better way to solve the same problem.</li>
				<li>May disappear entirely if the feature is too difficult to support or does bust enough boilerplate.</li>
			</ul>
			Features that receive positive community feedback and which seem to produce clean, flexible code will eventually become accepted
			as a core feature and move out of the experimental package.
			<dl>
				<dt><a href="Builder.html"><code>@Builder</code></a></dt>
				<dd>... and Bob's your uncle: No-hassle fancy-pants APIs for object creation!</dd>
				<dt><a href="Accessors.html"><code>@Accessors</code></a></dt>
				<dd>A more fluent API for getters and setters.</dd>
				<dt><a href="ExtensionMethod.html"><code>@ExtensionMethod</code></a></dt>
				<dd>Annoying API? Fix it yourself: Add new methods to existing types!</dd>
				<dt><a href="FieldDefaults.html"><code>@FieldDefaults</code></a></dt>
				<dd>New default field modifiers for the 21st century.</dd>
				<dt><a href="Wither.html"><code>@Wither</code></a></dt>
				<dd>Immutable 'setters' - methods that create a clone but with one changed field.</dd>
				<dt><a href="onX.html"><code>onMethod= / onConstructor= / onParam=</code></a></dt>
				<dd>Sup dawg, we heard you like annotations, so we put annotations in your annotations so you can annotate while you're annotating.</dd>
			</dl>
		</div>
		<div class="index overview">
			<h3>Putting the "Ex" in "Experimental": promoted or deleted experimental features.</h3>
			<dl>
				<dt><a href="../Value.html"><code>@Value</code></a>: Promoted</dt>
				<dd><code>@Value</code> has proven its value and has been moved to the main package.</li>
			</dl>
		</div>
		<div class="footer">
			<a href="../../credits.html" class="creditsLink">credits</a> | <span class="copyright">Copyright &copy; 2009-2013 The Project Lombok Authors, licensed under the <a href="http://www.opensource.org/licenses/mit-license.php">MIT license</a>.</span>
		</div>
		<div style="clear: both;"></div>
	</div>
</div>
<script type="text/javascript">
	var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
	document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
	try {
		var pageTracker = _gat._getTracker("UA-9884254-1");
		pageTracker._trackPageview();
	} catch(err) {}
</script>
</body></html>