JG
J. Gvozdiovas
info
Please Note
<p>This page displays the records of the person named above and is not linked to a unique person identifier. This record may need to be merged to a profile.</p>
2 records found
1
The regular constraint offers good balance between expressiveness and cost. Despite potential exponential blow-up, existing approaches use deterministic automata. Furthermore, the area of combining conflict-driven learning with regular is unexplored. We combine learning with non-determinism, to produce an NFA-based propagator with explanations, and compare its performance against decomposition of the constraint. Experimental results on Nonogram
instances indicate that our specialized propagator is significantly better than decomposing regular constraint. ...
instances indicate that our specialized propagator is significantly better than decomposing regular constraint. ...
The regular constraint offers good balance between expressiveness and cost. Despite potential exponential blow-up, existing approaches use deterministic automata. Furthermore, the area of combining conflict-driven learning with regular is unexplored. We combine learning with non-determinism, to produce an NFA-based propagator with explanations, and compare its performance against decomposition of the constraint. Experimental results on Nonogram
instances indicate that our specialized propagator is significantly better than decomposing regular constraint.
instances indicate that our specialized propagator is significantly better than decomposing regular constraint.
Haskell programming language has a long history of extensions which extend and modify its syntax and semantics. They range from small quality-of-life syntax improvements, to complete overhauls of the type system. Such extensions are commonly implemented directly as a part of Glasgow Haskell Compiler (GHC) or as plugins for GHC through its plugin API. This paper looks at the present ecosystem of such language extensions, identifying the key categories into which extensions can be separated, based on how often and in which ways they are used, and their functionality. We analysed which extensions are used in packages uploaded to Hackage, a central open-source Haskell archive. We further extracted the metadata about the packages, including the user-submitted tags and maintainer lists, to ascertain how and when are language extensions used. The result of our research is a combination of several proposed potential taxonomies, that can be used by academics and practitioners alike.
...
Haskell programming language has a long history of extensions which extend and modify its syntax and semantics. They range from small quality-of-life syntax improvements, to complete overhauls of the type system. Such extensions are commonly implemented directly as a part of Glasgow Haskell Compiler (GHC) or as plugins for GHC through its plugin API. This paper looks at the present ecosystem of such language extensions, identifying the key categories into which extensions can be separated, based on how often and in which ways they are used, and their functionality. We analysed which extensions are used in packages uploaded to Hackage, a central open-source Haskell archive. We further extracted the metadata about the packages, including the user-submitted tags and maintainer lists, to ascertain how and when are language extensions used. The result of our research is a combination of several proposed potential taxonomies, that can be used by academics and practitioners alike.