BombeCasting for me always means that I fucked up the data model somewhere.
Bombe(Exceptions apply for basic utility/library code, or interactions with other APIs.)
* punit_arya joined #java
ParaBuilder hierarchies have an use for casting as well.
jreicherBombe: it's not an explicit cast. As I said the return type of the method is non-covariant. That might be a nice way of "evidencing" that it's not a screw up, but an (unusual) way of expressing a constraint I want the compiler to check.
ParaI document my intentional casts with Class#cast()
jreicherInteresting. Not familiar with that syntax.
* sponkz joined #java
* hwpplayer1 joined #java
* leppard joined #java
* Ragnor joined #java
* punit_arya joined #java
* punit_arya joined #java
* johni__ joined #java
* MikeBux joined #java
* hwpplayer1 joined #java
* jreicher joined #java
* APic joined #java
jreicherBombe: did you mean to write Class#cast()? I assumed it was a syntax I didn't know, but I can't find anything on that.
jreicherSorry, Para ^
Parayes
ParaThat's how methods are generally referenced in javadocs and other such :P
ParaThat's also useful because it throws in place, so the wrong type doesn't go on an adventure through execution flow.
* punit_arya joined #java
* gurrkin joined #java
jreicherOh, that's what you mean. OK. But an upcast is not actually a cast in this sense.
jreicherNothing is done at runtime.
* hwpplayer1 joined #java
* pebble joined #java
* lucerne90 joined #java
* sponkz joined #java
* GreenResponse joined #java
* DrinkyBird joined #java
dreamrealLore (https://lore.org/) looks interesting but the reference implementation using dynamo means NEVERRRRRRRR
nevetLearn about Lore: next-generation open source version control
javabotdreamreal's title: "Lore | Next-Generation Open Source Version Control - Lore"
* sol6_vi_ joined #java
* jamezp joined #java
nimaje(why do webdevs think everything has to be invisible and their html a huge mess?)
ParaFor context, Lore is VCS for games. So excellent binary file, vendored dependencies, copyright/legally restricted parts of the whole with granular permission management etc.
cheeseri think we're due for new vcs systems to vie for the crown.
Paragit sucks for non-text so there's space
* creechy joined #java
cheesergit isn't great for usability so there's space. :)
ernimrilyou prefer sourcesafe? or subversion?
cheeserbitkeeper for life!
Paraemail!
fizziePerchance Perforce.
ernimril"oh, my quota is full, lets just send a large (several MB) to new zeeland, It will bounce in a few days..." :-) Sadly it does not work that way anymore
NeXeNi once tried to make a version control system, and failed
jreicherBy the time I started using version control, subversion was becoming popular, but I decided to start with RCS. I'm very glad I did because it showed me how hard the problem is to solve, and what a good (albeit incomplete) solution looks like. It was a very "clean" introduction to the space.
NeXeNi used cvs then git
NeXeNi wasn't on the bandwagon at any time, i sort of had to learn it because it was becoming the standard
jreicherI'd be surprised if anyone with "taste" is on the bandwagon. Git is not perfect.
jreicherI particularly hate the porcelaine.
jreicherporcelain
jreicherIf it weren't for the decent quality of the various frontends it probably wouldn't have taken off. Ironically it might be the scriptability of the command line that enabled them to emerge. I've never really checked the history.