Path: csiph.com!news.nrbbs.org!border-4.nntp.ord.giganews.com!nntp.giganews.com!Xl.tags.giganews.com!local-4.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 29 Jul 2026 19:55:43 +0000
From: steve g <Sgonedes1977@gmail.com>
Newsgroups: comp.lang.lisp
Subject: Re: Resources to learn common lisp?
References: <874inbqdz7.fsf@mariorosell.es> <110a9pp$ckmk$6@dont-email.me> <110es1g$1kk17$1@dont-email.me> <110fj4q$1r13s$5@dont-email.me> <110guci$26cjr$1@dont-email.me> <110i789$2iqm8$7@dont-email.me> <110j4qk$2q1p4$1@dont-email.me> <110l0v9$3av52$1@dont-email.me> <jwvbjdd5gx3.fsf-monnier+comp.lang.lisp@gnu.org> <110nf0q$3vra6$3@dont-email.me> <87y0gg62cx.fsf@nightsong.com> <110rfqf$142ot$1@dont-email.me> <111ne5o$vsm3$3@dont-email.me> <111pbk6$36pi7$1@dont-email.me> <87qzlqgiyx.fsf@gmail.com> <111t96n$6sqq$1@dont-email.me> <list-20260629095538@ram.dialup.fu-berlin.de> <111tev9$8hea$1@dont-email.me> <four-20260629110146@ram.dialup.fu-berlin.de> <111ti9v$9fsk$1@dont-email.me> <1124c30$2879p$7@dont-email.me>
Date: Wed, 29 Jul 2026 15:55:43 -0400
Message-ID: <871pclvadc.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:McsCyC+ujlhWNeNF1CVHBg2DzGE=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Lines: 13
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-rq5JlSXGjesLWTtw5Emg8CED1qIrMb+ZXXItTkcdwJHh4/VzIz/FDNdF5qHWyR6aicH+DhYH5YDIYUO!G9yj/bFp4sQ743vHDiiNkMdbHGSRq8s0zUxwYms18jAapDs=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Xref: csiph.com comp.lang.lisp:61234

Lawrence D’Oliveiro <ldo@nz.invalid> writes:

> On Mon, 29 Jun 2026 10:44:15 -0000 (UTC), tfb wrote:
>
>> Obviously this is just the same as using eq for numbers being a bad
>> idea in CL ...
>
> Luckily, that’s not a problem in Python, because it allows custom
> overloads for standard operators like “==”, which can do the right
> thing in a type-specific fashion.

seriously; operating overloading? is there a performance issue? No of
course not, it is done at runtime...