CS2030S Lab 4: Probably Solution

• Mark: 4%
Prerequisite:
• Caught up to Unit 26 of Lecture Notes
• Familiar with CS2030S Java style guide
Probably Just a Value but Maybe Nothing?
In this lab, you are given our own generic wrapper class, a Probably<T> . This is a wrapper class that can be used to store a value of any reference type. For now, our Probably<T> is not going to be a very useful abstraction. Not to worry. we will slowly add more functionalities to it.
Please read the following explanation on what the class Probably<T> is.
The Basics
The class Probably<T> stores either (1) none1 or (2) just a value of type T 2. So, it is probably just some value of type T or it maybe nothing. It:
• contains a private final eld of type T to store the value of reference type T .
• provides a private constructor.
• provides a class method called none() that returns nothing1.
• provides a class method called just(T value) that returns something that contains just the value2.
• Since there is a possibility that value is equal to null , in such case, we also return nothing.
• overrides the equals method from Object to compare if the two values inside are the same.
• Two values are the same according to their respective equals method.
• overrides the toString method so it returns the string representation of its values, between < and > .
The method none and just are called a factory method. A factory method is a method provided by a class for the creation of an instance of the class.
Probably<T> is also made to be immutable. Once created, the value of the eld value cannot be modied! This is achieved by:
• making the eld final .
• provide no getter and setter.
Relevant part of the code:


Shared Object
Using a public constructor to create an instance necessitates calling new and allocating a new object on the heap every time. A factory method, on the other hand, allows the exibility of reusing the same instance. With the availability of the factory methods, Probably<T> should keep the constructor private.
Additionally, the factory method as well as having Probably<T> immutable allows us to share a common object safely. The most common object here is the concept of nothing1. The factory methods return nothing when:
• the input argument to just(T value) is null , or
• the factory method none() is invoked
In both cases, we return a static instance called NONE . The sequence below shows how we can use a Probably using the methods above.
Testing Probably<T>
The following sample run shows the current capability of Probably<T> . You should also test using your own test cases to further understand Probably<T> .
1 jshell> Probably.just(4)
2 $.. ==> <4>
3 jshell> Probably.just(Probably.just(0))
4 $.. ==> <<0>>
5 jshell> Probably.just(Probably.just(Probably.just("null")))
6 $.. ==> <<<null>>>
7 jshell> Probably.just(Probably.just(Probably.none()))
8 $.. ==> <<<>>>
9 jshell> Probably.just(Probably.just(null))
10 $.. ==> <<>>
11 jshell> Probably.just(4).equals(Probably.just(4))
12 $.. ==> true
13 jshell> Probably.just(4).equals(4)
14 $.. ==> false
15 jshell> Probably.just(Probably.just(0)).equals(Probably.just(0)) 16 $.. ==> false
17 jshell>
18 Probably.just(Probably.just(0)).equals(Probably.just(Probably.just(0)))
19 $.. ==> true
20 jshell> Probably.just("string")
21 $.. ==> <string>
22 jshell> Probably.just("string").equals(Probably.just(4))
23 $.. ==> false
24 jshell> Probably.just("string").equals(Probably.just("null"))
25 $.. ==> false
26 jshell> Probably.just(null)
27 $.. ==> <>
28 jshell> Probably.none()
29 $.. ==> <>
30 jshell> Probably.none().equals(Probably.just(null))
31 $.. ==> true
32 jshell> Probably.none() == Probably.just(null)
$.. ==> true
You can check that our Probably<T> is correct by running:
1 javac -Xlint:rawtypes TestProbably.java
2 java TestProbably
Acting on the Value
Because Probably<T> is immutable, it is not useful for us. Once created, we cannot modify the value and we cannot even get the value back. To make the class more useful, we want to be able to act on the object. A simple act can be just printing using System.out.println .
One way for us to print the content of the value is to simply add a method called print .
However, this is not useful as we have to add a new method for each action that we want
Probably<T> to allow. One way to do this is to abstract a computation. Think of higherorder function.
Action Interface
One way to abstract a computation is to imagine having a class with a single method called call that perform an action that we want. If we receive an instance of this class, we can
invoke the method call to perform the action. Thus, we can say that a collection of all classes with a single method called call is an abstraction of an action.
You have 2 tasks in this section:
Create an interface Action<T> with a single abstract method called call inside the le Action.java .
• The method takes in a single parameter of generic type parameter T 3.
• The method does not return any type.
Create a non-generic class Print that implements Action with the method call that prints the string representation of the input argument into the standard output (i.e., System.out.println ) in the le Print.java .
Testing Action

Actionable Interface
With the Action interface, we can now perform a custome action. We can do this by adding in the Probably<T> class, a method that can accept an Action . Since this is a good behaviour to have, we want to create an interface representing all classes that can accept an Action . Let's call this interface as Actionable<T> .
You have 2 tasks in this section:
Create an interface Actionable<T> with a single abstract method called act inside the le Actionable.java .
• The method takes in a single parameter of type Action . This Action should accept a type T .
• The method does not return any type.
Modify Probably<T> to implement the interface Actionable . You need to implement the method act appropriately:
• if the value in Probably<T> is not null , we invoke call with the value.
• otherwise, do nothing.
Testing Actionable

Immutating the Value
value is declared with final . Instead, what we want to do is whenever there is a
mutation, we want to create a new instance of this class. This is the essence of an immutable class.
Immutator Interface
Similar to how we manage to add a custom action to Probably<T> , we want to add a custom mutator to the class. But since the class is immutable, let us calls this concept as immutation instead with the relevant interface called Immutator and Immutatorable .
An Immutator is similar to the Action<T> . However, unlike Action<T> that does not return anything, we want Immutator to return something. Consider any method with single parameter. We can write this method signature as:
1 R method(P param) { .. }
where R is the return type and P is the type of the parameter. By invoking this method, we can change a reference type of some value of type P into another value of type R . This is the basis of our Immutator . Such a powerful concept, not only can we change the value, we can also change the type!
You have 2 tasks in this section:
Create an interface Immutator<R,P> with a single abstract method called invoke inside the le Immutator.java .
• The method takes in a single parameter of generic type parameter T .
• The method returns a single value of generic type R .
• In other words, Immutator<R,P> is an abstraction of the method R method(P param) .
Create a generic class Improbable<T> that implements Immutator in the le Immutator.java with the method invoke that:
• takes in a single parameter of type T .
• returns a value of type Probably<T> .
• the method simply creates a Probably<T> from T regardless of what the type T is (including even when type T is already Probably<T>, but in this case what will be the actual return type?).
Testing Immutator
1 jshell> class Incr implements Immutator<Integer,Integer> {
2 ...> public Integer invoke(Integer t1) {
3 ...> return t1 + 1;
4 ...> }
5 ...> }
6 jshell> class Length implements Immutator<Integer,String> {
7 ...> public Integer invoke(String t1) {
8 ...> return t1.length();
9 ...> }
10 ...> }
11 jshell> new Incr().invoke(4)
12 $.. ==> 5
13 jshell> new Incr().invoke(new Incr().invoke(4))
14 $.. ==> 6
15 jshell> new Length().invoke("string")
16 $.. ==> 6
17 jshell> new Incr().invoke(new Length().invoke("string"))
18 $.. ==> 7
19 jshell> new Improbable<>().invoke(1)
20 $.. ==> <1>
21 jshell> new Improbable<String>().invoke(null)
22 $.. ==> <>
23 jshell> new Improbable<Integer>().invoke(1).transform(new Incr())
24 $.. ==> <2>
25 jshell> new Improbable<>().invoke(new Improbable<>().invoke(1)) 26 $.. ==> <<1>>
You can test your additions to Probably<T> more comprehensively by running:
1 javac -Xlint:rawtypes Test3.java
2 java Test3
Immutatorable Interface
Similar to before, we want to add a new method to Probably<T> but we also want to create an interface to represent all classes that can accept an Immutator . Let's call this method as transform .
Remember that Immutator<R,P> has a method called invoke that can produce a value of type R when given a value of type P . Our nal aim in the end is to transform Probably<T> to Probably<R> . For that, we want an immutator that transform T to R . Note that in this case, T corresponds to P in Immutator<R,P> .
You have 2 tasks in this section:
Create an interface Immutatorable<T> with a single abstract method called transform
inside the le Immutatorable.java .
• The method takes in a single parameter of type Immutator . This Immutator should accept a type T and return a type R .
• The method returns a single value of type Immutatorable<R> (or one of Immutatorable<R> subclasses as allowed by overriding).
Modify Probably<T> to implement the interface Immutatorable . You need to implement the method transform appropriately: local
• if the value in Probably<T> is not null , we invoke invoke with the value and return Probably<R> .
• otherwise, return NONE .
Testing Immutatorable
1 jshell> class Incr implements Immutator<Integer,Integer> {
2 ...> public Integer invoke(Integer t1) {
3 ...> return t1 + 1;
4 ...> }
5 ...> }
6 jshell> class Length implements Immutator<Integer,String> {
7 ...> public Integer invoke(String t1) {
8 ...> return t1.length();
9 ...> }
10 ...> }
11 jshell> Probably.just(4).transform(new Incr())
12 $.. ==> <5>
13 jshell> Probably.just(4).transform(new Incr()).transform(new Incr())
14 $.. ==> <6>
15 jshell> Probably.just("string").transform(new Length())
16 $.. ==> <6>
17 jshell> Probably.just("string").transform(new Length()).transform(new
18 Incr())
19 $.. ==> <7>
20 jshell> Probably.<Integer>none().transform(new Incr())
21 $.. ==> <>
22 jshell> Probably.<String>none().transform(new Length())
23 $.. ==> <>
24 jshell> Probably.<String>just(null).transform(new Length()).transform(new Incr())
$.. ==> <>
You can test your additions to Probably<T> more comprehensively by running:

Question
First, recap what we can do. We can create Probably<T> such that we can perform an action on it and mutate the value by creating a new instance each time the value changes. The next step is to ask questions regarding the value. The kind of questions we want to ask is a simple yes/no question.
Since at this point we have already created so many interfaces:
• Action
• Actionable
• Immutator
• Immutatorable
we do not want to create more interface. Instead, note that this is a special case of Immutator . This is simply an Immutator that returns a boolean.
Special Immutator
You have 2 tasks in this section:
Create a non-generic class IsModEq that implements this special Immutator that returns boolean values in the le IsModEq.java .
• The class has a public constructor that takes in two positive integer parameters div and check .
• The class implements the invoke inherited from Immutator .
• The method accepts a single integer parameter val .
• The method returns true if the remainder when val is divided by div is equal

• The method takes in a single parameter of type of the special Immutator introduced in this section.
• The method returns a single value of type Probably .
• The behaviour of the method can be captured by the table below:

Testing Question
1 jshell> class Incr implements Immutator<Integer,Integer> {
2 ...> public Integer invoke(Integer t1) {
3 ...> return t1 + 1;
4 ...> }
5 ...> }
6 jshell> class Length implements Immutator<Integer,String> {
7 ...> public Integer invoke(String t1) {
8 ...> return t1.length();
9 ...> }
10 ...> }
11 jshell> Probably.just(17).check(new IsModEq(3,2)) ∕∕ 17 % 3 is equal to 2
12 $.. ==> <17>
13 jshell> Probably.just(18).check(new IsModEq(3,2)) ∕∕ 18 % 3 is not equal
14 to 2
15 $.. ==> <>
16 jshell> Probably.just(16).transform(new Incr()).check(new IsModEq(3,2))
17 ∕∕ 17 % 3 is not equal to 2
18 $.. ==> <17>
19 jshell> Probably.just("string").transform(new Length()).check(new
20 IsModEq(3,2)) $.. ==> <8>
jshell> Probably.<Integer>just(null).check(new IsModEq(0,2)) $.. ==> <>

1 Probably.<>just(2030).check(new IsModEq(0,2))
Applicable
In this last section, we want to show some of the power of Probably<T> given our changes to it. Recap that we have at least 4 interfaces.
• Action
• Actionable
• Immutator
• Immutatorable
It's Probably an Immutator
Since Probably<T> can store any reference type T and Immutator is a reference type, we can store Immutator inside Probably<T> . What can we do with this Immutator inside Probably<T> ?
We have two cases here:
• if there is indeed an Immutator (i.e., it just2 some immutator), then we can use the immutator to mutate the value and the result of this really depends on the value.
• if there is no Immutator (_i.e., it is nothing1), then we simply return nothing.
Basically:
nothing in, nothing out.
You have 2 tasks in this section:
Create an interface Applicable<T> with a single abstract method apply inside the le Applicable.java .
• The method takes in a single parameter of type Immutator inside Probably<T> . This Immutator should accept a generic type Probably<T> and return a generic type Probably<R> .
• The method returns a single value of type Probably<R> .
• The method performs the operation described above.
Modify Probably<T> to implement the interface Applicable . You need to implement the method applu appropriately:
• if the value in Probably<T> is not null , we invoke invoke with the value and return Probably<R> .
• otherwise, return NONE .
Testing Applicable
1 jshell> class Incr implements Immutator<Integer,Integer> {
2 ...> public Integer invoke(Integer t1) {
3 ...> return t1 + 1;
4 ...> }
5 jshell> class Length implements Immutator<Integer,String> {
6 ...> public Integer invoke(String t1) {
7 ...> return t1.length();
8 ...> }
9 jshell> Probably<Immutator<Integer,Integer>> justIncr = Probably.just(new
10 Incr());
11 jshell> Probably<Immutator<Integer,String>> justLength =
12 Probably.just(new Length());
13 jshell> Probably<Immutator<Integer,Integer>> noIncr = Probably.none();
14 jshell> Probably<Immutator<Integer,String>> noLength = Probably.none();
15 jshell> Probably.just(17).<Integer>apply(justIncr)
16 $.. ==> <18>
17 jshell> Probably.<Integer>none().<Integer>apply(justIncr)
18 $.. ==> <>
19 jshell> Probably.just(17).<Integer>apply(noIncr)
20 $.. ==> <>
21 jshell> Probably.<Integer>none().<Integer>apply(noIncr)
22 $.. ==> <>
23 jshell> Probably.just("string").<Integer>apply(justLength)
24 $.. ==> <6>
25 jshell> Probably.<String>none().<Integer>apply(justLength) 26 $.. ==> <>

Hints
• This lab is more about the type rather than the code.
• You should think about the types that are required by each class and methods. In particular, you should think carefully about the generic type and wildcards if needed.
Files
A set of empty les have been given to you. You should only edit these les. You must not add any additional les.
The les Test1.java , Test2.java , etc., as well as CS2030STest.java , are provided for testing and they are not to be submitted. You can edit them to add your own test cases.
Lastly, the le Lab4.java is given for you and it should not be modied except for correcting any style problems detected by our style checker. This le will be the main entry point for our testing on CodeCrunch.
Following CS2030S Style Guide
You should make sure that your code follows the given Java style guide
Grading
This lab is worth 16 marks and contributes 4% to your nal grade. The marking scheme is as follows:
• Style: 2 marks
• Correctness: 14 marks
We will deduct 1 mark for each abuse or unnecessary use of @SuppressWarnings and for each raw type.
Note that the style marks are conditioned on the evidence of efforts in solving Lab 4.

We will refer to this as just, some, or something.
Here, a single type T includes the possibility that it uses wildcards involving T .