opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Move all files to sculpin/

Browse source
This commit is contained in:
Oliver Davies 2025-10-01 00:01:33 +01:00
parent c5d71803a5
commit 0f61b4e9ee
1514 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
source/_posts/2022-12-21.md
View file

@ -1,19 +0,0 @@
---
title: >
Duck typing
pubDate: 2022-12-21
permalink: >-
daily/2022/12/21/duck-typing
---
If it looks like a duck, walks like a duck, and quacks like a duck, it must be a duck.
If I pass a parameter into a function, as long as it works with the code within the function - it is of the correct type and has the expected properties and methods - it will work, although nothing is enforcing that the correct thing is passed in.
If not, you'd get an error that the method or property doesn't exist when trying to invoke or access it.
This is the opposite of strict typing, where you'd get a Type error if you passed the wrong thing.
Both are valid approaches, though I prefer to use types and get specific error messages and leverage tools like static analysis, which work better the more it understands your code.
In particular when writing and using open-source code that anyone can use however they like, I'd suggest leveraging types and type-checking, but it depends on what you, your team or your community prefer.