<lopex>
enebo: wrt joni one, we might comment that most are probably false positives
<enebo>
lopex: I just replied
<enebo>
lopex: I only looked at two of them but they both seemed to be the same issue
<lopex>
ok
<enebo>
lopex: at least it seems like value is not highlighted so I am guessing it does not realize other things can change value during those matches so 's' cannot change
<lopex>
enebo: what's the business model for such startups though, there's plethora of those tools
<enebo>
lopex: looks like we may not be the only people finding issues with that tool
<lopex>
well, at least they have feedback
<lopex>
or, free reviews :P
<enebo>
lopex: so perhaps they are building a for-sale tool and using OSS to figure out the bugs?
<enebo>
Maybe people will be so impressed they will buy some support
<lopex>
yeah, seems legit
<enebo>
so another angle here is they can sell analytical data on OSS projects
<enebo>
"Service Content may contain information about coding mistakes that will be publicly available through the lgtm service, and Semmle will have no liability for the results of such information being made publicly available. "
<lopex>
enebo: I'm looking for various ways to improve logging data access via ui
<enebo>
lopex: I feel like I missed half of a conversation
<enebo>
at work? or for fun?
<lopex>
enebo: at work
<enebo>
ah ok
<enebo>
and ebcidic spool files may be inspiration
<lopex>
enebo: I dont have a multimilion dollar machine at home :P
<enebo>
as400jr
<enebo>
jr = junior
<enebo>
I made that up
<enebo>
lopex: in theory it is released via sonatype but it will likely take some time for mirrors to see it
jmalves has joined #jruby
jmalves has quit [Ping timeout: 252 seconds]
<enebo>
lopex: he asked why so I replied. I believe what I said was correct but you can add another comment if I made a mistake.
<enebo>
not really criticizing them but it is almost ironic a tool to help people make higher quality code has a bug which makes me have to study code to tell them why their tool is not working.
<lopex>
enebo: free reviews like I said
<enebo>
lopex: yeah
Puffball has quit [Remote host closed the connection]
jmalves has joined #jruby
jmalves has quit [Ping timeout: 272 seconds]
jmalves has joined #jruby
jmalves has quit [Ping timeout: 245 seconds]
<lopex>
enebo: bumped
<enebo>
lopex: if what he says is true why does it not highlight value as a field?
<enebo>
maybe because it does not link to field since it is in another repo
<lopex>
enebo: from their query ?
<lopex>
or the coloring ?
<enebo>
lopex: well his query says they know but I just was confused why it was not highlighted in the alert as a field color
<enebo>
lopex: it may be because it cannot link to its definition perhaps
<lopex>
you're right
Puffball has joined #jruby
jmalves has joined #jruby
jmalves has quit [Ping timeout: 252 seconds]
drbobbeaty has quit [Ping timeout: 240 seconds]
drbobbeaty has joined #jruby
jmalves has joined #jruby
jmalves has quit [Ping timeout: 252 seconds]
nirvdrum has quit [Ping timeout: 268 seconds]
nirvdrum has joined #jruby
bbrowning is now known as bbrowning_away
jmalves has joined #jruby
jmalves has quit [Ping timeout: 245 seconds]
<lopex>
enebo: they ifdefed whole function sets based on sunday search macro definition
<enebo>
COPY CODE
<enebo>
lopex: YOU ARE THE MACRO EXPANDER
<lopex>
I'll try if it on static finals on the impl insides
<lopex>
that's at least 4 functions
<lopex>
and 8 for us if we want singlebyte specializations
<lopex>
or 6 in case they reuse old BM for backward searches
<lopex>
enebo: you're laughing ?
<enebo>
lopex: can we just somehow use a static utility function
<enebo>
lopex: or it probably needs to set multiple things