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
46
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
520
How RSpec Works
penelope_zone
0
6.4k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
75
Teaching RSpec to play nice with Rails
penelope_zone
2
120
Little machines that eat strings
penelope_zone
1
80
What is processor (brighton ruby edition)
penelope_zone
0
94
What is processor?
penelope_zone
1
340
extremely defensive coding - rubyconf edition
penelope_zone
0
240
Agile, etc.
penelope_zone
2
210
Other Decks in Technology
See All in Technology
AIで変わるテスト自動化:最新ツールの多様なアプローチ/ 20240910 Takahiro Kaneyama
shift_evolve
0
240
グイグイ系QAマネージャーの仕事
sadonosake
0
340
Discovering AI Models
picardparis
4
3.9k
Jetpack Compose Modifier 徹底解説 / Jetpack Compose Modifier
wiroha
0
200
なにもしてないのにNew Relicのデータ転送量が増えていたときに確認したこと
tk3fftk
2
230
サプライチェーン攻撃に備える
ryunen344
0
290
Tricentisにおけるテスト自動化へのAI活用ご紹介/20240910Shunsuke Katakura
shift_evolve
0
200
Road to Single Activity
yurihondo
2
240
OR学会2024秋_短期収益と将来のオフ方策評価性能を考慮したクーポン割当方策混合比の決定
recruitengineers
PRO
4
460
リアルお遍路+SORACOM IoT
ozk009
1
140
効果的なオンコール対応と障害対応
ryuichi1208
6
3.1k
Envoy External AuthZとgRPC Extensionを利用した「頑張らない」Microservices認証認可基盤
andoshin11
0
250
Featured
See All Featured
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
502
140k
BBQ
matthewcrist
83
9.2k
From Idea to $5000 a Month in 5 Months
shpigford
379
46k
10 Git Anti Patterns You Should be Aware of
lemiorhan
653
58k
Being A Developer After 40
akosma
84
590k
Statistics for Hackers
jakevdp
794
220k
Robots, Beer and Maslow
schacon
PRO
157
8.2k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
45
4.8k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
363
22k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
663
120k
Debugging Ruby Performance
tmm1
72
12k
[RailsConf 2023] Rails as a piece of cake
palkan
48
4.6k
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]