quattro_4 scribble

scribble 落書き (調べた事をただ落書きする)

thoughtbot Build Phase #48

F-ing Mush Mouth

Swiftとinitの問題

話す言語もプログラミング言語も、既知の言語から翻訳して考える
Swiftを考える時Objective-Cをもとに考えてしまう

maxpow4h/swiftz · GitHub
JSON parsing

アクセス修飾子 public/private/internal
Swiftのアクセス修飾子とObjCをためしてみたらFrameworkでちょっとした罠があった - Qiita

imperative 必須事項、義務、命令、規則、原則 http://eow.alc.co.jp/search?q=imperative


baseball
beer
nice ipa
hops
really diggin
access control
makes more better application
definitely
type system
swift
my prevailing opinion
coco
swift code not clicking
anything touching coco
real application
tony is writing lot of swift
instanciate by
type safety
view controller
event
dont wanna go back
sacrifice
concept
frustrating
initialized
obj c
point
not inplementation
class
create with nil
storyboards
fantastic lang
coco
compromise
perfect swift interface coco
json parsing
swiftz json parsing
curry
constructor
add to
mathmatic
json representation
user
cascades
succeed
whole thing fail
either user
ns error
internally
swiftz
use curry
one by one
user constructor
first name last name email
procedure
functional programming
wraped up
mutating
call init
duplicating constructor
nested closure
pass all constructor
user object
boilerpolate
not horrible
no idea
other problem
no idea
feel like
swift as if objc
swift for application
ruby code
best way to deal with
command line parser
big problem
same intuition
translation
objc
scan code shape
not happen in swift
5, 6 hours
dont know whats possible
no idea
good swift code
decent idea
frustrating
need something to work on
read
wwdc
no clue
other things
haskel
leaning swift
json parsing
good swift code
straight forward
knows swift syntax
strong functional concept
pick up language
polygra
php obj c
speak multiple language
spoken language
english in my head
translating spanish
difference
dad speak french
native speaker
computer language
same skill
mental set
math help
math foundation
bridge
how represent
safety net
imparative
instance methods
jump in ruby
create class encapsulate
concept
ruby objc
haskel
oo concept
functional
no loops
no conditionals
picture imparative code
time apply
connecting
coming
haskel doesnt define
describing
how things behave
how things do things
difference
teaching
bring back swift
didnt dive in
havent read
opinion
public private internal
weird
99% sure
declair
extension
drink beer
internet so slow
default internal
files
everything public
no access control obj c
xcode
nothing magic
header
source file
different file
undecirated
internal default
nice default
dont really care about
easier for beginners
fantastic
internal
scope module
dont want to black list
selectively
public
annotating
pointing java
extension
intended
makes perfect sense
breaking
base class
public
personally love header
works great
unit testing
not in same module
you do have to access
deal with
one more barrier
another thing
little more
declair things public
isnt meaningful
act the same
open class
depressing
scares me
limitation
side note
teriffying
apple doesnt test
attitude to test
swift responsibility
workaround
access control mechanism right
side effect
wavy
known issue
plan change
possibly
other access comtrol
really disappointed
solution here
unit test bundle magic switch
swift notes
xcode release note
never gonna promise
known issue
optimistic
roadmap
gm xcode6
putting swift first
compatibility legacy system