News for hackers. Stuff that matters.
Re:Tamgu, a functional, imperative, logical programming lang... by F-0X on Wednesday July 24, 2019 @04:19AM (#20513203)
> it might not happen until weeks into production.

It should never happen in production - there should be a test that proves this.

Re:Tamgu, a functional, imperative, logical programming lang... by willtim on Wednesday July 24, 2019 @09:50AM (#20515224)
To quote Dijkstra, testing shows the presence, not the absence of bugs. If you want to actually prove the absence of these classes of bugs then you need a static type system.
Re:Tamgu, a functional, imperative, logical programming lang... by em-bee on Wednesday July 24, 2019 @04:30AM (#20513253)
with declarative or static typing i don't need a test for this case.
Re:Tamgu, a functional, imperative, logical programming lang... by lispm on Wednesday July 24, 2019 @05:00AM (#20513391)
That's where a dynamically typed language with optional typing gets handy, when a compiler supports it...

In Common Lisp, the SBCL compiler would be such an example:

  * (defun foo () (let ((i 10) (s "20")) (concatenate 'string s i)))
  ; in: DEFUN FOO
  ;     (CONCATENATE 'STRING S I)
  ; 
  ; caught WARNING:
  ;   Derived type of I is
  ;     (VALUES (INTEGER 10 10) &OPTIONAL),
  ;   conflicting with its asserted type
  ;     SEQUENCE.
  ;   See also:
  ;     The SBCL Manual, Node "Handling of Types"
  ; 
  ; compilation unit finished
  ;   caught 1 WARNING condition
  FOO
  *