<whitequark>
it's kind of amazing how well irclogger holds up
<cr1901_modern>
I... did not know you could do that
<whitequark>
the search box is right there on the left!
<ktemkin>
MadHacker: I haven't tested on Windows, no, but I've used pretty much the same setup on FaceDancer with Windows, IIRC
<cr1901_modern>
It doesn't change the fact that I still didn't know you could do that :P.
<whitequark>
sure
<ktemkin>
there's a trick to being able to stall the *_LINE_CODING without upsetting Windows
<cr1901_modern>
I've always searched for my logs first, and then binary searched the irclogger for the text I searched. Like a "professional".
<cr1901_modern>
Now I know NOT to do that and actually use that damn search bar on the left
<ktemkin>
but I'd have to check OneNote notes, since it's been a couple of years
<whitequark>
i wrote irclogger in ~2 days in 2011 and i think overall it might be one of the most useful tools i produced, somehow
<whitequark>
in terms of utility * people reached
<cr1901_modern>
It's a good logger :D
<ktemkin>
is it using sinatra+cinch?
<ktemkin>
"developed an IRC logger in two days" sounds very that
* ktemkin
checks
<ktemkin>
yep
<whitequark>
lmao
<ktemkin>
I went through a ruby phase in the early 2010s as well =P
<whitequark>
i was doing PHP in high school and rails blew my mind
<ktemkin>
I had to do PHP around 2012, because I was implementing extensions for Moodle, which we used to teach at the university I was faculty at
<ktemkin>
never did wind up using rails
<ktemkin>
(I swear, I'm not as old as that makes me sound)
<whitequark>
hehe
<cr1901_modern>
I used LAMP minus "L" at my first job. I don't envy those days where I needed to code for 5 browsers at once (and IE of course ruined everything)
<sorear>
bsd? windows?
<whitequark>
i started on WAMP and then migrated to Windows plus Rails
<cr1901_modern>
Windows. Though I think it was supposed to be deployed on a SPARC Solaris system
<whitequark>
tbh i ended up using Sublime Text because of Railscasts and TextMate in them
_whitelogger has joined #nmigen
electronic_eel has quit [Ping timeout: 246 seconds]
electronic_eel has joined #nmigen
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #nmigen
zignig_ has joined #nmigen
zignig has quit [Ping timeout: 272 seconds]
zignig has joined #nmigen
zignig_ has quit [Ping timeout: 256 seconds]
jaseg has quit [Ping timeout: 256 seconds]
jaseg has joined #nmigen
<_whitenotifier-b>
[YoWASP/yosys] whitequark pushed 1 commit to develop [+0/-0/±1] https://git.io/JJsu6
proteus-guy has quit [Remote host closed the connection]
Asu has joined #nmigen
jeanthom has quit [Ping timeout: 272 seconds]
DaKnig has quit [Ping timeout: 240 seconds]
DaKnig has joined #nmigen
proteus-guy has joined #nmigen
chipmuenk has joined #nmigen
jeanthom has joined #nmigen
_whitelogger has joined #nmigen
<_whitenotifier-b>
[nmigen] jeanthom commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJsyE
<_whitenotifier-b>
[nmigen] jeanthom edited a comment on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJsyE
proteus-guy has quit [Ping timeout: 272 seconds]
_whitelogger has joined #nmigen
<lkcl_>
whitequark: evening. we have an interesting occurrence of someone experienced with nmigen and Formal Proofs having added an Assert on two python classes (expecting them to be Records or derived from Record)
<lkcl_>
regardless of whether it was Assert(x == y) or changing to Assert(x != y) because they were python objects not derived from Record (or UserValue), *both those tests silently passed*
<lkcl_>
the expected behaviour here would be to throw an exception (similar to "error, tried to yield bool") however now that i think about it i'm not sure that's even possible
<lkcl_>
unless the argument (objx == objy) is tested for being of "bool" type
<lkcl_>
anuejn: there's probably better ways to do that.
<anuejn>
thanks :)
<lkcl_>
my feeling is, it's the kind of really useful thing in processors (etc.) that kinda warrants adding to nmigen, if it isn't already in. i'm accumulating a lot of "small useful utils" in nmutil. queue.py in particular is a direct translation of Chisel3's Decoupled.scala class for example
<lkcl_>
fascinatingly despite originally being written in Chisel3, it's functionally sufficiently similar to nmigen FIFOs to actually warrant deriving from FIFOInterface base class
<lkcl_>
although a hack is added, it has the option to allow only one queue entry (even as a combinatorially-accessible one), by.. *sigh*.. setting the Memory depth to a minimum of 2.
<lkcl_>
miek: ohh yes, i remember seeing thi before
<anuejn>
miek: ah yes i remember reading that discussion, thanks :)
chipmuenk1 has joined #nmigen
chipmuenk has quit [Ping timeout: 256 seconds]
chipmuenk1 is now known as chipmuenk
hitomi2504 has quit [Quit: Nettalk6 - www.ntalk.de]
Asu has quit [Ping timeout: 240 seconds]
Asu has joined #nmigen
Asu has quit [Remote host closed the connection]
Asu has joined #nmigen
jeanthom has quit [Ping timeout: 260 seconds]
chipmuenk has quit [Read error: Connection reset by peer]
chipmuenk has joined #nmigen
Asu has quit [Remote host closed the connection]
Asu has joined #nmigen
<FL4SHK>
looking at supporting, uh, automatic destructor calls into this assembler thing I'm doing
<FL4SHK>
I've got, uh, automatic insertion of register saving/restoring
<FL4SHK>
and allocating space for local variables
<FL4SHK>
via a scopes feature that is also tied to local labels
<FL4SHK>
so I've got C++ style scoping in my assembler
<FL4SHK>
available via a `with` statement
<FL4SHK>
with scope() as s:
Asu has quit [Quit: Konversation terminated!]
Asu has joined #nmigen
jeanthom has joined #nmigen
chipmuenk has quit [Read error: Connection reset by peer]
chipmuenk1 has joined #nmigen
<_whitenotifier-b>
[nmigen] FFY00 commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGke
chipmuenk1 is now known as chipmuenk
<whitequark>
jeanthom: I guess, though it's unlikely anyone except me is going to pick it up
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGku
<whitequark>
lkcl_: two things
<whitequark>
first, Assert(False) should definitely be failing, so I don't know how both Assert(x==y) and Assert(x!=y) could pass
<whitequark>
you should minimize that and, if it's an nmigen bug, submit it
<whitequark>
second, we can definitely detect the case where in Assert(x), x is a bool, because that should probably just be a compile time assert (i.e. Python `assert` statement)
<whitequark>
please open an issue and we'll add that lint
<whitequark>
programmerjake's last comment actually I think warrants reevaluating what was previously discussed, since "the mathematical value is being preserved" can, perhaps, resurrect .as()
<whitequark>
please do comment on there with your view on the issue!
<whitequark>
ah, miek already linked it, oops
<lkcl_>
whitequark: appreciated
<_whitenotifier-b>
[nmigen] FFY00 commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGk1
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIf
<_whitenotifier-b>
[nmigen] FFY00 commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIO
<_whitenotifier-b>
[nmigen] FFY00 commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIc
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIu
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIz
<agg>
whitequark: do you imagine option (3) as being a python context manager (i.e. still suffers from rightward drift) or could it be a nmigen method you call (more like traditional C linters, or perhaps like numpy's seterr)?
<agg>
3 seems nicest to me and autogenerated code could easily disable whatever it needs for all its output, but having it inside a context manager seems a steep (indentation) price to pay
<_whitenotifier-b>
[nmigen] FFY00 commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIS
<_whitenotifier-b>
[nmigen] FFY00 edited a comment on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGIS
<whitequark>
agg: it would have to be a context manager, I think, though it might be possible to use the Module as a scope
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGLh
<_whitenotifier-b>
[nmigen] whitequark opened issue #436: [RFC] Extending the linter interface to allow per-scope settings - https://git.io/JJGtH
<_whitenotifier-b>
[nmigen] whitequark commented on issue #404: Unused cases in a switch do not trigger warnings - https://git.io/JJGtQ
jeanthom has quit [Remote host closed the connection]
jeanthom has joined #nmigen
<_whitenotifier-b>
[YoWASP/yosys] whitequark pushed 1 commit to release [+0/-0/±1] https://git.io/JJsu6