Add more documentation

Also, changed my mind on the way DiePool and its implementations should
be structured. The implementations go in the die pool file as internal
classes, because nobody should particularly care the specifics about
their die pool, only that it does what it says it should

1 files changed, 0 insertions, 25 deletions

diff --git a/dice/src/main/java/bjc/dicelang/neodice/diepool/ExpandDiePool.java b/dice/src/main/java/bjc/dicelang/neodice/diepool/ExpandDiePool.java
deleted file mode 100644
index 97acc79..0000000
--- a/dice/src/main/java/bjc/dicelang/neodice/diepool/ExpandDiePool.java
+++ /dev/null
@@ -1,25 +0,0 @@
-package bjc.dicelang.neodice.diepool;
-
-import java.util.*;
-import java.util.function.*;
-import java.util.stream.*;
-
-import bjc.dicelang.neodice.*;
-
-public class ExpandDiePool<SideType> implements DiePool<SideType> {
-	private final Die<SideType> contained;
-	
-	private final BiFunction<Die<SideType>, Random, Stream<SideType>> expander;
-
-	public ExpandDiePool(Die<SideType> contained,
-			BiFunction<Die<SideType>, Random, Stream<SideType>> expander) {
-		this.contained = contained;
-		this.expander = expander;
-	}
-
-
-	@Override
-	public Stream<SideType> roll(Random rng) {
-		return expander.apply(contained, rng);
-	}
-}