Change names of two value names that were way too long
Add printed output to the Result of evaluation

- This is not fully correct right now because of some theoretical problems with the instrumentation approach
- Changed the result class to accomodate the new API
- Add failing test cases related to mutability
- (of course) Add relevant tests for functionality
Add bintray plugin and use it to deploy latest version of the lib
Remove use of toSource function

- Not using the toString function to print an object is not a good idea
Better support for using vars

Vars were previously supported, just as long as you did not modify them, it's now possible do to just that without confusing the lib
Implement in a rush If/Then/Else support
Improve name of value definition
Fix some tests I had broken when pushing out the if/else support real quick

- Improved the internal API now that I had the time to think about it
Add a bunch of tests for some expected behaviour.

- Not sure yet about how to handle exceptions thrown inside of a top level expression or value definition
- A bunch of tests are failling right now, I will be fixing them in my upcoming commits
Implement exception handling for function definitions
Fix bug related to import statement

- A very simple additionnal case in the recursive analyse function
- Add comment on why relative imports fail
- Update import test to take into account the new IfElse feature
Improve test names
Add hardcoded Joda-time dependencie for proof of concept purposes
Upgrade specs from version 2.2.3 to 2.3.1
Add test case for issue #23

I need RangePositions to solve it easily
Code clean up

- Change transform function on StatementResult (Reduce duplication and make more generic, less typesafe however, need to write a compiler plugin to fix this one of these days)
- Change user facing interface for IfThenElseResult
- Update tests that had if expressions to reflect new expected behavior
- Put pendingUntilFixed on tests that are know to fail right now and that I want to revisit later
Use Try monad instead of WasThrown custom class to identify exceptions thrown in user code

- Aside from making the implementation slightly more clear, this greatly simplifies the generated code that is executed in order to garther the insights results
Added fucked up exception support! :-)

- From a toplevel perspective, a Result can now either be a StandardResult or an ExceptionResult
- Add isVar method on ValDef Tree
- Add tests for exception support
Use better strategy to retrieve results even if an exception was thrown that forced the end of the evaluation

- Wrap a Try block around all user code and return our map no matter what with the partial results, worse case scenario
- Revert back to one single Result class
- Add wasEvaluated method to help in pruning results
- fix issue with blocks and exceptions in evaluateBlock (wrap the whole thing in a try if it's a top level block, as opposed to changing the last child which didn't work if an exception was thrown in the middle of the block)
- Add test case for exception thrown from within a block
- update test cases for exceptions with new expectations
from sbt build to scala sbt build