Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
My Problem, My Solution
Search
Penelope Phippen
September 12, 2014
Technology
1
54
My Problem, My Solution
A talk about typing I gave at Frozen Rails 2014
Penelope Phippen
September 12, 2014
Tweet
Share
More Decks by Penelope Phippen
See All by Penelope Phippen
Introducing Rubyfmt
penelope_zone
0
560
How RSpec Works
penelope_zone
0
6.6k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
82
Teaching RSpec to play nice with Rails
penelope_zone
2
140
Little machines that eat strings
penelope_zone
1
99
What is processor (brighton ruby edition)
penelope_zone
0
110
What is processor?
penelope_zone
1
350
extremely defensive coding - rubyconf edition
penelope_zone
0
260
Agile, etc.
penelope_zone
2
220
Other Decks in Technology
See All in Technology
Delta airlines Customer®️ USA Contact Numbers: Complete 2025 Support Guide
deltahelp
0
1.1k
AWS CDK 開発を成功に導くトラブルシューティングガイド
wandora58
3
150
SREのためのeBPF活用ステップアップガイド
egmc
1
850
衛星運用をソフトウェアエンジニアに依頼したときにできあがるもの
sankichi92
1
220
Delta airlines®️ USA Contact Numbers: Complete 2025 Support Guide
airtravelguide
0
350
関数型プログラミングで 「脳がバグる」を乗り越える
manabeai
2
220
スタックチャン家庭用アシスタントへの道
kanekoh
0
110
ソフトウェアテストのAI活用_ver1.25
fumisuke
1
550
【LT会登壇資料】TROCCO新コネクタ「スマレジ」を活用した直営店データの分析
kazari0425
1
160
CDKTFについてざっくり理解する!!~CloudFormationからCDKTFへ変換するツールも作ってみた~
masakiokuda
1
200
ポストコロナ時代の SaaS におけるコスト削減の意義
izzii
1
200
大量配信システムにおけるSLOの実践:「見えない」信頼性をSLOで可視化
plaidtech
PRO
0
290
Featured
See All Featured
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Why Our Code Smells
bkeepers
PRO
336
57k
Practical Orchestrator
shlominoach
189
11k
Bash Introduction
62gerente
613
210k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
181
54k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
Gamification - CAS2011
davidbonilla
81
5.4k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.7k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.9k
Making the Leap to Tech Lead
cromwellryan
134
9.4k
Transcript
The maybe monad as a replacement for nil
My Problem My Solution
Everyone Stand Up
None
a!/samphippen
My Problem
Type Checking is the Antithesis of Object Oriented Programming
Type
Types
What is a type?
What is a data type?
A type is a set of possible values and operations
Class
Terms are literally interchangeable in Ruby
Terms are literally interchangeable in Ruby Konstantin
Fixnum
✕
+
/
—
1.class # => Fixnum
You know what all these things do
1+1 # => 2
Array
count
each
In Ruby some types are interchangeable
Typeclass
A set of types and common operations
There is some expectation of what the operations will do
Duck typing
All number types in Ruby form a typeclass
Fixnum Float BigDecimal
Numeric Op Numeric = Numeric
Positive Numeric + Positive Numeric = Positive Numeric =
Also collections
Hash Set Array
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Type Checking
This term has two meanings
Compile time type checking
public static final List<string> seriouslyiamsoboredwh ocares
Like in Java
Clearly we don’t do this in Ruby
So what do I mean?
ActiveRecord::Base #find_by
pony = Pony.find_by(:id => smth) pony.neigh
pony = Pony.find_by(:id => smth) if pony pony.neigh else puts
“No Pony can’t neigh” end
The problem here is two return types
nil Pony < AR::Base
We’re forced to add a type check
Also, I think this is the wrong type check
pony = Pony.find_by(:id => smth) if !pony.nil? pony.neigh else puts
“No Pony can’t neigh” end
A more explicit type check
But still wrong
pony = Pony.find_by(:id => smth) if !pony.nil? pony.neigh else puts
“No Pony can’t neigh” end
pony = Pony.find_by(:id => smth) if pony.respond_to?(:neigh) pony.neigh else puts
“No Pony can’t neigh” end
This type checking adds unnecessary complexity to our app
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Antithesis
I am using it to mean “DOING IT WRONG”
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
Object oriented programming
Konstantin Haase says:
Data abstraction and control abstraction
Alan Kay says:
Everything is an object
Objects communicate by sending and receiving messages
def bees if :bar == a.foo else end end
def bees a.foo nil end
Tell don’t ask
Objects have their own memory (in terms of objects).
Data hiding
Every object is an instance of a class (which must
be an object).
The class holds the shared behavior for its instances (in
the form of objects in a program list)
To eval a program list, control is passed to the
first object and the remainder is treated as its message.
Type Checking is the Antithesis of Object Oriented Programming
Type Checking is the Antithesis of Object Oriented Programming
My Problem
My Problem
My Solution
Just always make your methods return things of a consistent
type class
Thanks!
No obviously there’s more
Third party APIs do this all the time
pony = Pony.find_by(:id => smth) if pony pony.neigh else puts
“No Pony can’t neigh” end
The problem here is two return types
As a client of this API I am forced to
add a type check
nil is such a common case
How do we fix it?
Null object pattern
I think this one is quite well known
class Pony def horse_power 0.5 end end
Pony.find_by( :key => value ) || NullPony.new
class NullPony def horse_power 0 end end
NullPony quacks the same as Pony
Solves the typing problem
Summing over ponies will only count Pony objects
0 might be the wrong default
Pony * NullPony = 0
Decided the default for horse_power when defining the class
Change is inevitable
Can’t predict how NullPony will be used in the future
Maybe Typeclass
Solves same problem
Allows for runtime defaults
#map(&blk) -> Maybe #value_or(a) -> a
class Just def initialize(value) @value = value end def map(&blk)
def value_or(x) Just.new(blk.call(@value)) @value end end end
class Nothing def map(&blk) self end def value_or(x) x end
end
A consistent interface for dealing with missing values
NoMethodError: undefined method `foo' for nil:NilClass
NoMethodError: undefined method `foo' for nil:NilClass
[Maybe, Nothing, Maybe]
call map on all of them
collapse with value_or
To Recap:
Null object can replace nils if you know the defaults
at class definition time
Maybe if you want defaults at run time
Your job is not to make Alan Kay happy
RSpec RSpec ! ! RSpec 3
tinyurl.com/ samfr2014
Let’s have some questions a!/samphippen
[email protected]