서브메뉴
검색
An Investigation of the Pragmatics of Debugging With Contracts and Gradual Types
An Investigation of the Pragmatics of Debugging With Contracts and Gradual Types
상세정보
- 자료유형
- 학위논문 서양
- 최종처리일시
- 20250211151412
- ISBN
- 9798382761565
- DDC
- 004
- 저자명
- Lazarek, Lukas.
- 서명/저자
- An Investigation of the Pragmatics of Debugging With Contracts and Gradual Types
- 발행사항
- [Sl] : Northwestern University, 2024
- 발행사항
- Ann Arbor : ProQuest Dissertations & Theses, 2024
- 형태사항
- 202 p
- 주기사항
- Source: Dissertations Abstracts International, Volume: 85-11, Section: A.
- 주기사항
- Advisor: Dimoulas, Christos.
- 학위논문주기
- Thesis (Ph.D.)--Northwestern University, 2024.
- 초록/해제
- 요약This dissertation demonstrates that a new empirical method, called the Rational Programmer, can examine the pragmatics of contracts and gradual typing in the context of debugging at scale and in an automated manner. The method begins with a hypothesis about how a specification technique's error information assists in locating bugs. Then, the method calls for designing an algorithm that simulates an idealized programmer using the technique to locate bugs. We can then test the algorithm on a variety of scenarios in a large-scale automated experiment, the results of which provide evidence to either support or refute the hypothesis.Concretely, this dissertation provides data from evaluations of two techniques: contracts and gradual typing. In the case of contracts, the rational programmer helps reveal that while carefully-designed blame information does live up to its hypothesized debugging benefits, primitive stacktrace information appears to do so nearly as well. In the case of gradual typing, the evaluation results suggest that when mistakes occur in code, academic approaches' specialized error information provide marginally better debugging help; when mistakes occur in type annotations, however, the results do suggest that the special error information offers valuable debugging information. These results demonstrate the value of the rational programmer and point to several directions for future investigations.
- 일반주제명
- Computer science
- 일반주제명
- Language
- 일반주제명
- Information science
- 키워드
- Debugging
- 키워드
- Gradual typing
- 키워드
- Language design
- 기타저자
- Northwestern University Computer Science
- 기본자료저록
- Dissertations Abstracts International. 85-11A.
- 전자적 위치 및 접속
- 로그인 후 원문을 볼 수 있습니다.
MARC
008250123s2024 us c eng d■001000017161552
■00520250211151412
■006m o d
■007cr#unu||||||||
■020 ▼a9798382761565
■035 ▼a(MiAaPQ)AAI31292818
■040 ▼aMiAaPQ▼cMiAaPQ
■0820 ▼a004
■1001 ▼aLazarek, Lukas.
■24513▼aAn Investigation of the Pragmatics of Debugging With Contracts and Gradual Types
■260 ▼a[Sl]▼bNorthwestern University▼c2024
■260 1▼aAnn Arbor▼bProQuest Dissertations & Theses▼c2024
■300 ▼a202 p
■500 ▼aSource: Dissertations Abstracts International, Volume: 85-11, Section: A.
■500 ▼aAdvisor: Dimoulas, Christos.
■5021 ▼aThesis (Ph.D.)--Northwestern University, 2024.
■520 ▼aThis dissertation demonstrates that a new empirical method, called the Rational Programmer, can examine the pragmatics of contracts and gradual typing in the context of debugging at scale and in an automated manner. The method begins with a hypothesis about how a specification technique's error information assists in locating bugs. Then, the method calls for designing an algorithm that simulates an idealized programmer using the technique to locate bugs. We can then test the algorithm on a variety of scenarios in a large-scale automated experiment, the results of which provide evidence to either support or refute the hypothesis.Concretely, this dissertation provides data from evaluations of two techniques: contracts and gradual typing. In the case of contracts, the rational programmer helps reveal that while carefully-designed blame information does live up to its hypothesized debugging benefits, primitive stacktrace information appears to do so nearly as well. In the case of gradual typing, the evaluation results suggest that when mistakes occur in code, academic approaches' specialized error information provide marginally better debugging help; when mistakes occur in type annotations, however, the results do suggest that the special error information offers valuable debugging information. These results demonstrate the value of the rational programmer and point to several directions for future investigations.
■590 ▼aSchool code: 0163.
■650 4▼aComputer science
■650 4▼aLanguage
■650 4▼aInformation science
■653 ▼aDebugging
■653 ▼aGradual typing
■653 ▼aLanguage design
■653 ▼aProgramming languages
■653 ▼aSoftware contracts
■690 ▼a0984
■690 ▼a0679
■690 ▼a0723
■71020▼aNorthwestern University▼bComputer Science.
■7730 ▼tDissertations Abstracts International▼g85-11A.
■790 ▼a0163
■791 ▼aPh.D.
■792 ▼a2024
■793 ▼aEnglish
■85640▼uhttp://www.riss.kr/pdu/ddodLink.do?id=T17161552▼nKERIS▼z이 자료의 원문은 한국교육학술정보원에서 제공합니다.
