tag:blogger.com,1999:blog-6373963829340632529.post2658089081403778482..comments2024-01-30T05:40:30.415-03:00Comments on Algorithmically challenged: Case Classes and ProductDanielhttp://www.blogger.com/profile/07505997833685327219noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6373963829340632529.post-50342114200624285142021-12-09T03:45:51.224-03:002021-12-09T03:45:51.224-03:00Appreciate you sharing, great article.Much thanks ...Appreciate you sharing, great article.Much thanks again. Really Cool.<br /><a href="https://www.kitsonlinetrainings.com/course/sap-abap-online-training-course" rel="nofollow">SAP ABAP training</a><br /><a href="https://www.kitsonlinetrainings.com/course/sap-abap-online-training-course" rel="nofollow">SAP ABAP online training in hyderabad</a>KITS Technologieshttps://www.blogger.com/profile/01255736173821596606noreply@blogger.comtag:blogger.com,1999:blog-6373963829340632529.post-1057175248108445872009-06-13T15:53:07.501-03:002009-06-13T15:53:07.501-03:00Products are cool, and little known. But the sad t...Products are cool, and little known. But the sad thing is that they used to be even more powerful. A couple of Scala versions back, a case class with N parameters would extend ProductN[T1, T2, ..., Tn]. That mean one could trivialy have generic methods that took any case class (or tuple) with specific types. <br /><br />And, less trivially, one could use some implicits magic to have types ranging over arities of Products, which is kind of a poor man's version of dependent typing.<br /><br />But, alas, case class inheritance broke all that, and now only TupleN extends a ProductN trait. Sad...Anonymousnoreply@blogger.com